Methods, systems, and media for managing wind speed data, seismic data and other natural phenomena data

ABSTRACT

A system for collecting and managing seismic data via an external communications network comprises one or more seismic stations, each including a seismic measurement apparatus producing seismic signals, a station processor converting the signals to seismic data, a station memory securely storing the seismic data on site and a station communication interface transmitting the seismic data onto an external network. The system further comprises one or more data servers, each including a server computing device, a server communication interface receiving the seismic data from the seismic stations and a server memory storing the received seismic data. The data server can determine if the received seismic data satisfies predetermined conditions for certification and/or triggering a payout in accordance with a contract, and can thereafter transmit the appropriate data signals to another location on the external communications network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/533,556, filed on Aug. 6, 2019, entitled METHODS, SYSTEMS, AND MEDIAFOR MANAGING WIND SPEED DATA, SEISMIC DATA AND OTHER NATURAL PHENOMENADATA, now U.S. Pat. No. 11,112,512, issued on Sep. 7, 2021, which is acontinuation-in-part of U.S. patent application Ser. No. 15/285,762filed on Oct. 5, 2016, entitled METHODS, SYSTEMS, AND MEDIA FOR MANAGINGWIND SPEED DATA, issued as U.S. Pat. No. 10,375,182 on Aug. 6, 2019.Application Ser. No. 15/285,762 claims benefit of U.S. ProvisionalApplication No. 62/239,072, filed on Oct. 8, 2015, entitled METHODS,SYSTEMS, AND MEDIA FOR MANAGING WIND SPEED DATA. All the foregoing,including patent application Ser. Nos. 16/533,556, 15/285,762 and62/239,072, are incorporated by reference herein in their entirety.

TECHNICAL FIELD

The disclosed subject matter relates to methods, systems, and media formanaging wind speed data, seismic data and other natural phenomena data.

BACKGROUND

Devices such as anemometers for the measurement of wind speeds areknown, and devices for recording wind speed data are also known.Recorded wind speed data from such devices may be valuable for resolvinginsurance claims resulting from storm damage. However, during severeweather, or in the aftermath of severe storms, the recording of windspeeds may be interrupted and/or the recorded wind speed data may belost due to physical damage, lightning strikes, water intrusion, powerloss, looting, vandalism or other causes adversely affecting the windspeed measurement and recording devices and/or the media upon which thewind speed data is stored. A need therefore exists, for methods, systemsand media for managing wind speed data that are more resistant todamage, interruption and/or data loss during and after severe weather.

Even when recorded wind speed data remains intact, following a severestorm it may be difficult to obtain access to the locations where therecorded wind speed data is stored. This can result in delays inobtaining recorded wind speed data, which in turn can delay theresolution of insurance claims resulting from storm damage. A needtherefore exists, for methods, systems and media for managing wind speeddata that can transfer the wind speed data in a timely manner from theassociated wind measurement stations to remote locations where the datacan be evaluated. A need further exists, for methods, systems and mediafor managing wind speed data that can evaluate wind speed data todetermine if certification of the wind speed data is indicated and/or todetermine if payment under a contract is indicated.

Seismic waves are waves of energy that travel across the surface of theEarth and through the layers of the Earth as a result of earthquakes,volcanoes, quakes, tremors, temblors and similar natural shakingphenomena and also man-made shaking events such as explosions(hereinafter collectively termed “earthquakes” or “seismic events”).Seismic waves can directly produce destructive effects including groundshaking (i.e., ground acceleration and velocity), ground rupture andsoil liquefaction. Seismic waves can also indirectly result inlandslides, structure collapses, fires, tsunami and floods. Devices suchas seismometers and accelerometers are known for the measurement ofseismic waves and the associated ground accelerations and velocitiesoccurring during earthquakes and similar destructive seismic events.Devices are also known for recording seismic wave data, groundacceleration data and/or ground velocity data (hereinafter collectivelytermed “seismic data”) relating to measured seismic waves, accelerationsand velocities. Recorded seismic data may be valuable for resolvinginsurance claims resulting from direct and indirect earthquake damage.However, during earthquakes, or in the aftermath of a seismic event, therecording of seismic data may be interrupted and/or the recorded seismicdata may be lost due to physical damage, structure collapse, fire, waterintrusion, power loss, looting, vandalism or other causes adverselyaffecting the seismic measurement and seismic data recording devicesand/or the media upon which the seismic data is stored. A need thereforeexists, for methods, systems and media for collecting and managingseismic data that are more resistant to damage, interruption and/or dataloss during and after a seismic event.

In some areas, and especially in known seismically-active regions,government, university and/or research entities may operate one or moreseismic measurement and/or recording devices. By monitoring the seismicwaves received at such devices during a seismic event, estimates can bemade regarding the overall characteristics of a given earthquake orseismic event such as the approximate magnitude, depth and geographicepicenter. Using the maximum intensity observed near the epicenter ofthe event and from the extent of the geographic area where the seismicevent was felt, a so-called isoseismal map of the event may be producedto show the approximate intensity of local ground shaking across theregion, i.e., for geographic areas where no direct measurement or datais available. However, the actual shaking intensity and/or durationexperienced at a given geographic location of interest can vary greatlyfrom that estimated in an isoseismal map. In particular, from onegeographic location of interest to another, the property damageresulting from a single earthquake or seismic event can varysignificantly depending on a number of factors including, but notlimited to, the overall magnitude of the seismic event, the distancefrom the epicenter of the seismic event, the soil conditions at thelocation of interest, soil conditions intervening between the eventepicenter and the location of interest, geological structures at thelocation of interest and geological structures intervening between theevent epicenter and the location of interest.

In view of the factors previously described, using isoseismal mapestimates for resolving earthquake/seismic event insurance claims at aspecific geographic location of interest event can be problematicbecause the isoseismal map is not based on actual seismic data relevantto likely property damage measured at the location. Therefore, anisoseismal map-based estimate will not accurately predict the actualconditions experienced during a seismic event and the likely resultingproperty damage at a specific geographic location. A need thereforeexists, for methods, systems and media for collecting and managingseismic data at a given geographic location of interest that arerelevant to property damage estimates at the given geographic locationof interest.

Even when seismic data is collected for a specific geographic locationof interest and remains intact, following a significant seismic event itmay be difficult to obtain access to the locations where the recordedseismic data is stored. This can result in delays in obtaining recordedseismic data, which in turn can delay the resolution of insurance claimsresulting from earthquake damage at the location. A need thereforeexists, for methods, systems and media for managing seismic data thatcan transfer the seismic data in a timely manner from the associatedseismic measurement stations to remote locations where the data can beevaluated. A need further exists, for methods, systems and media formanaging seismic data that can evaluate seismic data to determine ifcertification of the seismic data is indicated and/or to determine ifpayment under a contract is indicated.

SUMMARY

In some embodiments a wind speed data system can gather wind speed datafrom an anemometer located at a wind speed station, store the wind speeddata on a storage device located at the wind speed station, and transmitthe wind speed data to a data server such that the wind speed data canbe stored redundantly and protected from data loss resulting from stormsor other causes of data loss.

In some other embodiments, a storage device located at the wind speedstation can be protected within a housing located below ground. Forexample, the storage device can be protected by a waterproof, damageresistant housing that can detach from the other components of the windstation in the event of damage being caused to the wind station byexcessive wind speeds or other forces.

In still other embodiments, the gathered wind speed data can be used tocreate a wind speed damage model such that whenever excessive windspeeds are detected at a wind station, an amount of property damage canbe estimated based on the wind speeds detected and the wind speed damagemodel.

In another aspect, a wind station system for collecting and managingwind speed data at a geographic location having a ground level isprovided, the system comprising a wind-resistant pole disposed at thegeographic location, the pole having a base portion disposed below theground level and a riser portion extending upward from the base portion.An anemometer is mounted on the riser portion of the pole above theground level, the anemometer producing wind speed signals indicative ofwind speed at the anemometer. A computing device is operativelyconnected to the anemometer for the receiving the wind speed signalsfrom the anemometer and producing wind speed data corresponding to thereceived wind speed signals. A housing is disposed at the geographiclocation but physically separated from both the pole and the anemometerand a storage device is disposed inside the housing and operativelyconnected to the computing device for receiving wind speed data from thecomputing device and storing the wind speed data.

In one embodiment, the housing containing the storage device iswaterproof and disposed below the ground level.

In another embodiment, the wind station system further comprises anelectrical storage battery disposed at the geographic location andoperatively connected to at least one of the anemometer, computingdevice and storage device for supplying electrical power thereto, and aphotovoltaic solar panel disposed at the geographic location andoperatively connected to the storage battery for charging the storagebattery with electrical power.

In yet another embodiment, the operatively connecting between thecomputing device and the storage device for communication of the windspeed data from the computing device to the storage device isaccomplished by a wireless connection.

In a further embodiment, the wireless connection for communication ofthe wind speed data from the computing device to the storage device isone of cellular mobile device network, Bluetooth, Wi-Fi and near fieldcommunication.

In a still further embodiment, the computing device further comprises acommunication interface adapted to transmit wind speed data from thestorage device to another location using an external communicationnetwork.

In another embodiment, the storage device includes a memory for storingthe wind speed data, and the memory is at least one of a random accessmemory, a read-only memory, a flash memory, a hard disk drive, asolid-state drive, a removable memory card, a removable USB memorystick, and an optical drive and optical media.

In another aspect, a system for collecting and managing wind speed datavia an external communications network is provided. The system comprisesone or more wind station, each respective wind station being disposed ata respective wind station location and including, respectively, ananemometer disposed at the respective wind station location andproducing wind speed signals indicative of wind speeds at the respectivewind station location, a station computing device disposed at therespective wind station location and operatively connected to theanemometer for receiving the wind speed signals and producing wind speeddata corresponding to the wind speed signals, a station memory disposedat the respective wind station location and operatively connected to thestation computing device for storing the wind speed data, and a stationcommunication interface disposed at the respective wind stationlocation, the station communication interface being operativelyconnected to the station computing device to receive wind speed datatherefrom, and being operatively connected to an external communicationnetwork to the transmit wind speed data to the external communicationsnetwork. The system further comprises one or more data server, eachrespective data server being disposed at a respective data serverlocation and including, respectively, a server computing device disposedat the respective data server location, a server communication interfacedisposed at the respective data server location, the servercommunication interface being operatively connected to the externalcommunication network to receive respective wind speed data from the oneor more wind stations and operatively connected to the server computingdevice to provide the received respective wind speed data to the servercomputing device, and a server memory disposed at the respective dataserver location and operatively connected to the server computing devicefor storing the received respective wind speed data. The one or moredata server can transmit the stored received respective wind speed datato another location on the external communications network.

In one embodiment, the one or more wind station are further adapted tostore a plurality of respective individual anemometer readings in therespective station memory over a predetermined time period, to convertthe plurality the respective individual anemometer readings over thepredetermined time period into a respective average wind speed for thepredetermined time period, and to transmit the respective average windspeed for the predetermined time period to the one or more data serverover the external communications network.

In another embodiment, the one or more wind station are further adaptedto store a plurality of respective individual anemometer readings in therespective station memory over a predetermined time period, to convertthe plurality the respective individual anemometer readings over thepredetermined time period into a respective maximum wind speed for thepredetermined time period, and to transmit the respective maximum windspeed for the predetermined time period to the one or more data serverover the external communications network.

In yet another embodiment, the system further comprises one or morecertification server, each respective certification server beingdisposed at a respective certification server location and including,respectively, a certification server computing device disposed at therespective certification server location and a certification servercommunication interface disposed at the respective certification serverlocation, the certification server communication interface beingoperatively connected to the external communication network to receiverespective wind speed data from the one or more data servers andoperatively connected to the certification server computing device toprovide the received respective wind speed data to the certificationserver computing device. Each of the one or more certification servercan generate a respective data model, the respective data modelcomprising at least one of a historical storm model and a wind speeddamage model. Each of the one or more certification server can generatea respective certification report based on the received respective windspeed data and the generated respective data models. The one or morecertification server can transmit the generated respective certificationreport to another location on the external communications network.

In a further embodiment, the system further comprises one or more payoutserver, each respective payout server being disposed at a respectivepayout server location and including, respectively, a payout servercomputing device disposed at the respective payout server location and apayout server communication interface disposed at the respective payoutserver location, the payout server communication interface beingoperatively connected to the external communication network to receivethe respective certification reports from the one or more certificationserver and to provide the received respective certification reports tothe payout server computing device. Each of the one or more payoutserver can determine if a received respective certification reportsatisfied the terms of a respective associated contract.

In a still further embodiment, each of the one or more payout server,upon determining that the received respective certification reportsatisfies the terms of the respective associated contract, triggers arespective payout in accordance with the respective associated contractat another location by communicating over the external communicationnetwork.

In yet another aspect, a method for collecting and managing wind speeddata is provided. The method comprises measuring wind speeds at a one ormore geographic location and producing respective wind speed signalsindicative of the respective measured wind speeds at each respective oneor more geographic location, wherein the respective wind speed signalsare one of electric signals and electronic signals. The method furthercomprises converting respective wind speed signals into respective windspeed data at each respective one or more geographic location, whereinthe respective wind speed data is digital data, storing the respectivewind speed data at each respective one or more geographic location,wherein the respective wind speed data is stored in a digital dataformat, and transmitting the respective stored wind speed data at eachrespective one or more geographic location as digital data onto anexternal communications network. The method further comprises receiving,at one or more data server, the respective wind speed data as digitaldata for the respective one or more geographic location from theexternal communication network, storing the received respective windspeed data for the respective one or more geographic location on the oneor more data server and determining, at the one or more data server, ifthe respective one or more wind speed data for each of the respectiveone or more geographic location are to be sent for certification. Whenit is determined that the one or more respective wind speed data for therespective one or more geographic location are to be sent forcertification, the method further comprises transmitting the respectiveone or more wind speed data for the respective one or more geographiclocation as digital data onto an external communications network andreceiving, at one or more certification server, the respective windspeed data for the respective one or more geographic location as digitaldata from the external communication network.

In one embodiment, the method further comprises storing a plurality ofthe respective wind speed data for a particular one of the one or moregeographic location over a predetermined time period, converting thestored plurality of the respective wind speed data for the particularone of the one or more geographic location over the predetermined timeperiod into at least one of an average wind speed for the predeterminedtime period at the particular one of the one or more geographiclocation, and a maximum wind speed for the predetermined time period atthe particular one of the one or more geographic location, anddetermining, for the predetermined time period at the particular one ofthe one or more geographic locations, if the respective average windspeed or maximum wind speed exceeds a predetermined threshold for therespective average wind speed or maximum wind speed. When it isdetermined that the respective average wind speed or maximum wind speedexceeded a predetermined threshold for the respective average wind speedor maximum wind speed, the method further comprises transmitting andalert signal as digital data to a user device using the externalcommunications network.

In another embodiment, the method further comprises generating, inresponse to receiving at the one or more certification server therespective wind speed data for the respective one or more geographiclocation from the external communication network, at least one of ahistorical storm model and a wind speed damage model, generating acertification report for the respective one or more geographic locationbased on both the respective wind speed data for the respective one ormore geographic location and the at least one of generated historicalstorm model and wind speed damage model and transmitting thecertification report for the respective one or more geographic locationas digital data onto the external communications network.

In yet another embodiment, the method further comprises determining, inresponse to receiving the certification report for the respective one ormore geographic location from the external communication network,whether the terms of an associated contract are satisfied. When it isdetermined in response to receiving the certification report that theterms of an associated contract are satisfied, the method furthercomprises triggering a payout in accordance with the associated contractby communicating digital data onto the external communications network.

In another aspect, a seismic station system for collecting and managingseismic data at a geographic location is provided, the system comprisinga seismic measuring apparatus disposed at the geographic location,wherein the seismic measuring apparatus is one of a seismometer and anaccelerometer. The seismic measuring apparatus produces seismic signalsindicative of seismic or acceleration conditions at the geographiclocation. A processor is operatively connected to the seismic measuringapparatus for the receiving the seismic signals from the seismicmeasuring apparatus and producing seismic data corresponding to thereceived seismic signals. A housing is disposed at the geographiclocation and a memory is disposed inside the housing and operativelyconnected to the processor for receiving seismic data from the processorand storing the seismic data. A computing device is operably connectedto the memory for communication with the memory for transmitting theseismic data from the memory to the computing device.

In one embodiment, the housing containing the memory is formed of adamage-resistant material, wherein the damage-resistant material isprimarily concrete or steel.

In another embodiment, the seismic station system further comprises anelectrical storage battery disposed at the geographic location andoperatively connected to at least one of the seismic measurementapparatus, processor and memory for supplying electrical power thereto.

In yet another embodiment, the operative connection between the memoryand the computing device for transmitting the seismic data from thememory to the computing device includes a wireless connection.

In still another embodiment, the wireless connection for transmittingthe seismic data from the memory to the computing device is one ofcellular mobile device network, Bluetooth, Wi-Fi and near fieldcommunication.

In a further embodiment, the computing device further comprises acommunication interface adapted to transmit the seismic data from thememory to another location using an external communication network.

In a still further embodiment, the memory for storing the seismic datais at least one of a random access memory, a read-only memory, a flashmemory, a hard disk drive, a solid-state drive, a removable memory card,a removable USB memory stick, and an optical drive and an optical media.

In another aspect, a system for collecting and managing seismic data viaan external communications network comprises one or more seismicstation. Each respective seismic station is disposed at a respectiveseismic station location and includes, respectively: a seismicmeasurement apparatus disposed at the respective seismic stationlocation and producing seismic signals indicative of seismic oracceleration conditions at the respective seismic station location; astation processor disposed at the respective seismic station locationand operatively connected to the seismic measuring apparatus forreceiving the seismic signals and producing seismic data correspondingto the seismic signals; a station memory disposed at the respectiveseismic station location and operatively connected to the stationprocessor for storing the seismic data; and a station computing devicehaving a communication interface disposed at the respective seismicstation location, the communication interface being operativelyconnected to the station processor to receive the seismic datatherefrom, and being operatively connected to an external communicationnetwork to the transmit the seismic data to the external communicationsnetwork. The system further comprises one or more data server, eachrespective data server being disposed at a respective data serverlocation and including, respectively: a server computing device disposedat the respective data server location; a server communication interfacedisposed at the respective data server location, the servercommunication interface being operatively connected to the externalcommunication network to receive respective seismic data from the one ormore seismic stations and operatively connected to the server computingdevice to provide the received respective seismic data to the servercomputing device; and a server memory disposed at the respective dataserver location and operatively connected to the server computing devicefor storing the received respective seismic data. The one or more dataserver can transmit the stored received respective seismic data toanother location on the external communications network.

In one embodiment, the one or more seismic station are further adaptedto store a plurality of respective individual seismic data values in therespective station memory over a predetermined time period, to convertthe plurality the respective individual seismic data values over thepredetermined time period into a respective average seismic data valuefor the predetermined time period, and to transmit the respectiveaverage seismic data value for the predetermined time period to the oneor more data server over the external communications network.

In another embodiment, the one or more seismic station are furtheradapted to store a plurality of respective individual seismic datavalues in the respective station memory over a predetermined timeperiod, to convert the plurality the respective individual seismic datavalues over the predetermined time period into a respective maximumseismic data value for the predetermined time period, and to transmitthe respective maximum seismic data value for the predetermined timeperiod to the one or more data server over the external communicationsnetwork.

In yet another embodiment, the system further comprises one or morecertification server, each respective certification server beingdisposed at a respective certification server location and including,respectively: a certification server computing device disposed at therespective certification server location; and a certification servercommunication interface disposed at the respective certification serverlocation, the certification server communication interface beingoperatively connected to the external communication network to receiverespective seismic data from the one or more data servers andoperatively connected to the certification server computing device toprovide the received respective seismic data to the certification servercomputing device. Each of the one or more certification server cangenerate a respective data model, the respective data model comprisingat least one of a historical earthquake or seismic event model and anearthquake or seismic event damage model. Each of the one or morecertification server can generate a respective certification reportbased on the received respective seismic data and the generatedrespective data models. The one or more certification server cantransmit the generated respective certification report to anotherlocation on the external communications network.

In still another embodiment, the system further comprises one or morepayout server, each respective payout server being disposed at arespective payout server location and including, respectively: a payoutserver computing device disposed at the respective payout serverlocation; and a payout server communication interface disposed at therespective payout server location, the payout server communicationinterface being operatively connected to the external communicationnetwork to receive the respective certification reports from the one ormore certification server and to provide the received respectivecertification reports to the payout server computing device. Each of theone or more payout server can determine if a received respectivecertification report satisfied the terms of a respective associatedcontract.

In a further embodiment, each of the one or more payout server, upondetermining that the received respective certification report satisfiesthe terms of the respective associated contract, triggers a respectivepayout in accordance with the respective associated contract at anotherlocation by communicating over the external communication network.

In yet another aspect, a method for collecting and managing seismic datacomprises measuring seismic or acceleration conditions at a one or moregeographic location and producing respective seismic signals indicativeof the respective measured seismic or acceleration conditions at eachrespective one or more geographic location, wherein the respectiveseismic signals are one of electric signals and electronic signals. Therespective seismic signals are converted into respective seismic data ateach respective one or more geographic location, wherein the respectiveseismic data is digital data. The respective seismic data are stored ateach respective one or more geographic location, wherein the respectiveseismic data is stored in a digital data format. The respective storedseismic data are transmitted at each respective one or more geographiclocation as digital data onto an external communications network. At oneor more data server, the respective seismic data is received as digitaldata for the respective one or more geographic location from theexternal communication network. The received respective seismic data forthe respective one or more geographic location is stored on the one ormore data server. At the one or more data server, it is determined ifthe respective one or more seismic data for each of the respective oneor more geographic location are to be sent for certification, and whenit is determined that the one or more respective seismic data for therespective one or more geographic location are to be sent forcertification, the respective one or more seismic data for therespective one or more geographic location are transmitted as digitaldata onto an external communications network. At one or morecertification server, the respective seismic data for the respective oneor more geographic location is received as digital data from theexternal communication network.

In one embodiment, the method further comprises storing a plurality ofthe respective seismic data values for a particular one of the one ormore geographic location over a predetermined time period, andconverting the stored plurality of the respective seismic data valuesfor the particular one of the one or more geographic location over thepredetermined time period into at least one of an average seismic valuefor the predetermined time period at the particular one of the one ormore geographic location, and a maximum seismic value for thepredetermined time period at the particular one of the one or moregeographic location. The method further comprises determining, for thepredetermined time period at the particular one of the one or moregeographic locations, if the respective average seismic value or maximumseismic value exceeds a predetermined threshold for the respectiveaverage seismic value or maximum seismic value. When it is determinedthat the respective average seismic value or maximum seismic valueexceeded a predetermined threshold for the respective average seismicvalue or maximum seismic value, an alert signal is transmitted asdigital data to a user device using the external communications network.

In another embodiment, the method further comprises generating, inresponse to receiving at the one or more certification server therespective seismic data for the respective one or more geographiclocation from the external communication network, at least one of ahistorical earthquake or seismic event model and a earthquake or seismicevent damage model. A certification report is generated for therespective one or more geographic location based on both the respectiveseismic data for the respective one or more geographic location and theat least one of generated historical earthquake or seismic event modeland earthquake or seismic event damage model. The certification reportfor the respective one or more geographic location is transmitted asdigital data onto the external communications network.

In yet another embodiment, the method further comprises determining, inresponse to receiving the certification report for the respective one ormore geographic location from the external communication network,whether the terms of an associated contract are satisfied. When it isdetermined in response to receiving the certification report that theterms of an associated contract are satisfied, a payout is triggered inaccordance with the associated contract by communicating digital dataonto the external communications network.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, features, and advantages of the disclosed subjectmatter can be more fully appreciated with reference to the followingdetailed description of the disclosed subject matter when considered inconnection with the following drawings, in which like reference numeralsidentify like elements.

FIG. 1 shows an example of a wind station system for managing wind speeddata in accordance with some embodiments of the disclosed subjectmatter;

FIG. 1A shows an enlarged view of an anemometer suitable for use in someembodiments of the wind station system of FIG. 1;

FIG. 2 shows an example of hardware for managing wind speed data thatcan be used in accordance with some embodiments of the disclosed subjectmatter;

FIG. 3 shows an example of hardware implemented as a computing device inaccordance with some embodiments of the disclosed subject matter;

FIG. 4 shows an example of a process for managing wind speed data inaccordance with some embodiments of the disclosed subject matter;

FIG. 5 shows an example of a process for managing wind speed dataincluding triggering wind speed payouts based on wind speed data inaccordance with some embodiments of the disclosed subject matter;

FIG. 6 shows an example of a seismic station system for managing seismicdata in accordance with another aspect of the disclosed subject matter;

FIG. 7 shows an example of hardware for managing seismic data that canbe used in accordance with some embodiments of the disclosed subjectmatter;

FIG. 8 shows an example of a process for managing seismic data inaccordance with some embodiments of the disclosed subject matter;

FIG. 9 shows an example of a process for managing seismic data includingtriggering seismic event payouts based on seismic data in accordancewith some embodiments of the disclosed subject matter; and

FIG. 10 shows an example of hardware for managing both wind speed dataand seismic data that can be used in accordance with some embodiments ofthe disclosed subject matter.

DETAILED DESCRIPTION

In accordance with various embodiments of the disclosed subject matter,mechanisms (which can include methods, systems, and media) for managingwind speed data are described herein.

Referring now FIG. 1, there is illustrated an example of a wind stationsystem 100 for managing wind speed data in accordance with someembodiments of the disclosed subject matter. In some embodiments, thewind station system 100 is disposed at a particular geographic locationand manages wind speed data for winds occurring at the particulargeographic location. As shown, in some embodiments, system 100 caninclude a lightning terminal 102, an anemometer 104, a solar panel 106,a computing device 108, a ground wire 110, a pole 112, a pole foundation114, a housing 116 and a storage device 118. In some embodiments, all ofthese elements can be disposed at the particular geographic location,whereas in other embodiments, some of the elements may be disposed atdifferent geographic locations. It should be understood that althoughonly one of each of these elements is shown in FIG. 1, more than one ofeach of these elements can be used in some embodiments.

In some embodiments, any lightning terminal 102 suitable for conductingthe electric charge of a lightning strike away from other components canbe used. For example, the lighting terminal 102 can comprise anelectrically conductible rod, an electrically conductible wire, and/orany other electrically conductible part or assembly of parts.

In some embodiments, the lightning terminal 102 can be connected to theground wire 110 such that in the event of a lightning strike, theelectric charge will be grounded to the earth 120. In some embodiments,any suitable ground wire 110 can be used. For example, the ground wire110 can be a copper wire, a shielded wire, an insulated wire and/or anyother type of wire suitable for grounding an electric charge.

In some embodiments, the ground wire 110 can be inserted at any suitabledepth into the earth 120. For example, a ground wire 110 can be insertedinto the earth 120 to a depth of 20 feet below the ground level 113(i.e., surface) at the location.

Referring still to FIG. 1, and now also to FIG. 1A, in some embodiments,any anemometer 104 suitable for measuring wind speeds can be used. Forexample, referring now specifically to FIG. 1A, in the illustratedembodiment the anemometer 104 may include a propeller 122. In some suchembodiments, the anemometer 104 can produce an electrical signal whenthe propeller 122 is rotated by wind. In a more particular example, thepropeller 122 can produce an AC sine wave electrical signal. In anothermore particular example, the propeller 122 can be configured to producean electrical signal directly proportional to wind speed. The anemometer104 may further include a tail assembly 124 and a swivel bearing 126rotatably connected to the pole 112, whereby the action of the wind onthe tail assembly causes the anemometer to rotate horizontally on theswivel bearing to keep the propeller 122 facing into the wind. In someembodiments, the anemometer 104 can be implemented without a propellerusing other moving apparatus, for example, moving cups, vanes, rotorsand/or with non-moving apparatus, for example, a pitot tube assembly, tomeasure the wind speed. In other embodiments, the anemometer 104 canproduce electrical signals (e.g., analog voltage, current, frequency orphase signals) or electronic signals (e.g., digital electric signals)proportional to the measured wind speed and/or indicative of themeasured wind speed at the anemometer's geographic location.

Referring now to FIG. 3, there is illustrated one example of computerhardware 300 implemented as the computing device 108 in accordance withone embodiment. In some other embodiments, any suitable computing device108 can be used. As illustrated in FIG. 3, the computer hardware 300 caninclude a hardware processor 302, a memory and/or storage 304, an inputdevice controller 306, an input device 308, display/audio drivers 310,display and audio output circuitry 312, a communication interface(s)314, an antenna 316 and a bus 318.

The hardware processor 302 can include any suitable hardware processor,such as a microprocessor, a micro-controller, digital signalprocessor(s), dedicated logic, and/or any other suitable circuitry forcontrolling the functioning of a general purpose computer or a specialpurpose computer in some embodiments. In some embodiments, the hardwareprocessor 302 can be controlled by a program stored in the memory and/orstorage 304. For example, the program can cause the hardware processor302 to perform the mechanisms and/or processes described herein formanaging wind speed data, and/or perform any other suitable actions.

The memory and/or storage 304 can be any suitable memory and/or storagefor storing application information, programs, data, and/or any othersuitable information in some embodiments. For example, the memory and/orstorage 304 can include random access memory (“RAM”), read-only memory(“ROM”), flash memory, hard disk storage, optical media and/or any othersuitable memory.

The input device controller 306 can be any suitable circuitry forcontrolling and receiving input from one or more input devices 308 insome embodiments. For example, the input device controller 306 can becircuitry for receiving input from a touchscreen, from a keyboard, froma mouse, from one or more buttons, from a voice recognition circuit,from a microphone, from a camera, from an optical sensor, from anaccelerometer, from a temperature sensor, from a near field sensor, froma wind speed sensor (e.g., the anemometer 104 of FIG. 1) and/or from anyother type of input device.

The display/audio drivers 310 can be any suitable circuitry forcontrolling and driving output to one or more display/audio outputdevices 312 in some embodiments. For example, the display/audio drivers310 can be circuitry for driving a touchscreen, a flat-panel display, acathode ray tube display, a projector, a speaker or speakers and/or anyother suitable display and/or presentation devices.

The communication interface(s) 314 can be any suitable circuitry forinterfacing with one or more communication networks, such as thecommunication network 210 shown in FIG. 2 and described below. Forexample, the interface(s) 314 can include network interface cardcircuitry, wireless communication circuitry and/or any other suitabletype of communication network circuitry. The communication interface(s)314 can also include circuitry for interfacing with external devicesincluding the storage device 118 and/or the memory 130 for storingand/or retrieving wind speed data from the storage device and/or thememory. In some embodiments, the wind speed data can be stored in thestorage device 118 and/or the memory 130 as digital data and/or can betransmitted to, or received from, the communication network 210 asdigital data.

The antenna 316 can be any of one or more suitable antennas forwirelessly communicating with a communication network (e.g., thecommunication network 210 of FIG. 2 as described below) in someembodiments. In some embodiments, the antenna 316 can be omitted.

The bus 318 can be any suitable mechanism for communicating between twoor more components 302, 304, 306, 310 and 314 in some embodiments. Thecommunication between the components of the computer hardware 300 alongthe data bus 318 can be implemented as digital data.

Any other suitable components can be included in hardware 300 inaccordance with some embodiments.

Referring again to FIG. 1, the pole 112 can include a base portiondisposed below the surface of the ground (i.e., below the ground level113) and a riser portion extending upward from the base portion. In someembodiments, the base portion of the pole 112 can be supported by a polefoundation 114. Any suitable pole foundation 114 can be used in someembodiments. For example, the pole foundation 114 can be implemented asstone (e.g., FDOT #57 stone) backfilled about the pole 112. In someembodiments, the pole 112 may be a concrete pole or a steel pole.

In some embodiments, the pole foundation 114 can be configured such thatthe pole 112 can sustain wind speeds of one hundred sixty miles perhour. For example, the pole foundation 114 can comprise a two andone-half foot diameter cylinder extending fourteen feet underground(i.e., below the surface of the ground) and configured such that thepole 112 is above a one foot layer of the foundation material.

In some embodiments, the housing 116 for the storage device 118 can beimplemented as any housing suitable for underground containment. Forexample, the housing 116 can include any suitable waterproof material,or combination of waterproof materials such as rubber, polyvinylchloride (PVC), polyurethane, silicone rubber, and/or any other suitablewaterproof material. As another example, the housing 116 can include anysuitable non-waterproof material coated with a waterproof material. As amore particular example, the housing 116 can include a concrete housingcoated with a bitumen membrane, a PVC membrane, a liquid rubber coating,an elastomeric coating, and/or any other coating material or method. Asyet another example, the housing 116 can be any suitable safe (i.e.,vault), which can be encased in cement to hold it in place. In preferredembodiments, the housing 116 is disposed below the ground level 113 toprovide increased protection and security.

In some embodiments, the housing 116 can include a security device 128.For example, the housing 116 can include a safe/vault equipped with alocking device. As another example, the housing 116 can include alocking mechanism (e.g., a combination locking mechanism or a keylocking mechanism).

In some embodiments, the housing 116 can contain any suitable storagedevice 118. For example, the storage device 118 can be any suitablememory 130 and/or storage for storing application information, programs,data and/or any other suitable information in some embodiments. Thestorage of the information, programs, data and/or other suitableinformation on the storage device 118 and/or the memory 130 can beimplemented as digital data in any digital data format. As anotherexample, the storage device 118 and memory 130 can include random accessmemory (“RAM”), read-only memory (“ROM”), flash memory, hard diskdrive(s) (“HDD”), solid-state drive(s) (“SSD”), memory card(s) (forexample, but not limited to, “CompactFlash” cards, “SecureDigital”cards, “Memory Stick” cards), a removable USB memory stick, opticaldrives and optical media (for example, but not limited to, CD drives andCD discs, DVD drives and DVD discs, and Blu-ray drives and Blu-raydiscs) and/or any other suitable memory.

In some embodiments, the storage device 118 can be configured inside thehousing 116 such that the storage device can remain operable in theevent of damage being caused to the above-ground components of the windstation 100. For example, the housing 116 can remain unattached to thepole 112 or pole foundation 114. In such an example, the memory 130 caninclude a wireless communication module, such as Bluetooth, Wi-Fi, nearfield communication radio, cellular mobile device network and/or anyother wireless communication module suitable for allowing the memory toreceive data (indicated in FIG. 1 by arrow 132) wirelessly from thecomputing device 108 and/or the anemometer 104. As another example, thememory 130 can be communicatively attached to the computing device 108,anemometer 104 and/or other components of the wind station 100 such thatin the event of damage to the other components, the memory can bedetached. As a more particular example, the memory 130 and/or thehousing 116 can be attached to other components at least in part by ashear pin, the shear pin configured such that the memory and/or thehousing can detach from the other components in the event thatsignificant force (e.g., tensile force and/or shearing force) is appliedto the memory and/or the housing.

In some embodiments, any suitable solar panel configuration can be usedfor the solar panel 106. For example, the solar panel 106 can be mountedon the pole 112 such that the solar panel can detach from the poleand/or other components in the event of extreme winds. As anotherexample, a solar panel 106 can be configured with a battery 134operatively connected (indicated in FIG. 1 by arrows 136) to some or allof the other components (e.g., the anemometer 104, computing device 108and/or storage device 118), such that the solar panel can provide powerto the other components without interruption. As a more particularexample, the solar panel 106 can be configured with a battery 134 suchthat the battery can store enough charge to power the other componentsfor ten or more days.

Referring now to FIG. 2, there is illustrated one example of systemhardware 200 for managing wind speed data that can be used in accordancewith some embodiments of the disclosed subject matter. As illustrated,the system hardware 200 can include one or more: data servers 202, userdevices 204, certification servers 206, contract payout servers 208 andwind stations 209 outfitted with computing devices 108.

In some embodiments, the wind station 209 can be any suitable windstation configured with a computing device 108. For example, as shown inFIG. 1, the wind station 209 can be the wind station system 100 disposedat a particular geographic location.

In some embodiments, the data server 202 can be any suitable server forstoring data and/or delivering the data to a user device 204. In someembodiments, the data stored by the data server 202 and/or delivered tothe user device 204 can be implemented as digital data in any digitaldata format. For example, the data server 202 can be a server thatdelivers data to a user device 204 and/or receives data from a windstation 209 via a communication network 210. In some embodiments, thedata server 202 can include a server computing device, a servercommunication interface operatively connected to the communicationnetwork 210 to receive respective wind speed data from one or more windstations 209 and operatively connected to the server computing device toprovide the received respective wind speed data to the server computingdevice and a server memory disposed at the respective data serverlocation and operatively connected to the server computing device forstoring the received respective wind speed data. Data stored and/ordelivered by the data server 202 can be any suitable data, such as windspeed data, wind direction data, historical weather data, contract data,contract payout data and/or any other suitable data. Data can berecorded and uploaded to the data server 202 by any suitable entity(e.g., a wind station computing device 108). In some embodiments, thedata server 202 can be disposed at a geographic location that is remotefrom (i.e., geographically distant from) the wind station system 100,whereas in other embodiments, the data server can be disposed at thesame geographic location as the wind station system. In some embodimentshaving more than one wind station system 100, each respective windstation system can be disposed at a different respective wind stationlocation, and the data server 202 can be disposed at a data serverlocation that is remote from at least one of the respective wind stationlocations. In some embodiments having more than one wind station system100 and more than one data server 202, each respective wind stationsystem can be disposed at a different respective wind station location,and each respective data server 202 can be disposed at a differentrespective data server location, wherein the respective wind stationlocations and data server locations are all geographically remote fromone another. In some other embodiments, the data server 202 can beomitted.

The communication network 210 can be any suitable combination of one ormore wired and/or wireless networks in some embodiments. For example,the communication network 210 can include anyone or more of theInternet, an intranet, a wide-area network (WAN), a local-area network(LAN), a wireless network, a digital subscriber line (DSL) network, aframe relay network, an asynchronous transfer mode (ATM) network, avirtual private network (VPN), and/or any other suitable communicationnetwork. The user device 204 can be connected by one or morecommunications links 212 to the communication network 210, which can belinked via one or more communications links to the data server 202,and/or wind stations 209. The communications links 212 can be anycommunications links suitable for communicating data among the userdevice 204, data server 202 and wind stations 209, such as networklinks, dial-up links, wireless links, hard-wired links, any othersuitable communications links, or any suitable combination of suchlinks. In some embodiments, the data communicated across thecommunication network 210 and/or communication links 212 can beimplemented as digital data in any digital data format.

The user device 204 can include anyone or more user devices suitable forrequesting data, searching for data, viewing data, retransmitting data,manipulating data, receiving a user input and/or any other suitablefunctions. For example, in some embodiments, the user device 204 can beimplemented as a mobile device, such as a mobile phone, a tabletcomputer, a laptop computer and/or any other suitable mobile device. Asanother example, in some embodiments, the user device 204 can beimplemented as a non-mobile device such as a desktop computer and/or anyother suitable non-mobile device. In some embodiments, the user device204 can be disposed at a geographic location that is remote from (i.e.,geographically distant from) the wind station system 100 and/or the dataserver 202, whereas in other embodiments, the user device can bedisposed at the same geographic location as the wind station systemand/or the data server.

In some embodiments, the contract payout server 208 can be any suitableserver for causing a contract to be paid out based on wind speed data.For example, the contract payout server 208 can be a server thatreceives wind speed data from a data server 202 via a communicationnetwork 210, and/or determines whether a contract should be paid outbased on wind speed data and/or causes a third party server 214 topayout a contract by communicating with the third party server over acommunication network 210. The storage of the wind speed data and otherinformation, programs, data and/or other suitable information on thecontract payout server 208 can be implemented as digital data in anydigital data format. In some embodiments, the payout server 208 caninclude a payout server computing device, a payout server communicationinterface operatively connected to the communication network 210 toreceive respective certification reports from one or more certificationservers 206 and operatively connected to the payout server computingdevice to provide the received respective certification reports to thepayout server computing device, and/or a payout server memoryoperatively connected to the payout server computing device for storingthe received respective certification reports. In some embodiments, thepayout server computing device can determine if a received respectivecertification report satisfied the terms of an associated contract, andif so, the payout server can trigger a payout at another location bycommunicating over the communication network 210. In some embodiments,the contract payout server 208 can be disposed at a geographic locationthat is remote from (i.e., geographically distant from) the wind stationsystem 100, the data server 202 and/or the user device 204, whereas inother embodiments, the contract payout server can be disposed at thesame geographic location as the wind station system, the data serverand/or the user device.

In some embodiments, the certification server 206 can be any suitableserver for certifying wind speed data. For example, the certificationserver 206 can be a server that receives wind speed data from a dataserver 202 via a communication network 210, and/or stores historicalwind speed data and/or determines whether wind speed data is accurate.The storage of the wind speed data and other information, programs, dataand/or other suitable information on the certification server 206 can beimplemented as digital data in any digital data format. In someembodiments, the certification server 206 can include a certificationserver computing device, a certification server communication interfaceoperatively connected to the communication network 210 to receiverespective wind speed data from one or more data servers 202 andoperatively connected to the certification server computing device toprovide the received respective wind speed data to the certificationserver computing device, and/or a certification server memoryoperatively connected to the certification server computing device forstoring the received respective wind speed data. In some embodiments,the certification server computing device can generate a data model, forexample a historical storm model or a wind speed damage model, and thegenerated data model can be transmitted by the certification servercommunication interface to another location on the communication network210. In some embodiments, the certification server computing device cangenerate a certification report based on the received wind speed dataand the generated data model, and the certification report can betransmitted by the certification server communication interface toanother location on the communication network 210. In some embodiments,the certification server 206 can be disposed at a geographic locationthat is remote from (i.e., geographically distant from) the wind stationsystem 100, the data server 202, the user device 204 and/or the contractpayout server 208, whereas in other embodiments, the contract payoutserver can be disposed at the same geographic location as the windstation system, the data server, the user device and/or the contractpayout server.

Although the data server 202 and the user device 204 are illustrated asseparate devices in FIG. 2, the functions performed by the data serverand the user device can be performed using any suitable number ofdevices in some embodiments. For example, in some embodiments, thefunctions performed by either the data server 202 or the user device 204can be performed on a single device. As another example, in someembodiments, multiple devices can be used to implement the functionsperformed by the data server 202 and the user device 204.

Although the data server 202, certification server 206, and the contractpayout server 208 are illustrated as separate devices in FIG. 2, thefunctions performed by the data server, certification server and thecontract payout server can be performed using any suitable number ofdevices in some embodiments. For example, in some embodiments, thefunctions performed by either the data server 202, the certificationserver 206, or the contract payout server 208 can be performed on asingle device. As another example, in some embodiments, multiple devicescan be used to implement the functions performed by the data server 202,the certification server 206 and the contract payout server 208.

Although only two wind stations 209, one certification server 206, onecontract payout server 208, one data server 202, one user device 204 andone third-party server 214 are shown in FIG. 2 to avoidover-complicating the figure, any suitable number and/or any suitabletypes of wind stations, data servers, user devices and third-partyservers can be used in some embodiments.

The data server 202, the user device 204, and the wind station computingdevices 108 can be implemented using any suitable hardware in someembodiments. For example, in some embodiments, the data server 202, theuser device 204 and the wind station computing devices 108 can beimplemented using any suitable general purpose computer or specialpurpose computer. For example, the wind station computing device 108 maybe implemented using a special purpose computer. Any such generalpurpose computer or special purpose computer can include any suitablehardware. For example, referring again to FIG. 3, as illustrated inexample computer hardware 300, such hardware can include a hardwareprocessor 302, a memory and/or storage 304, an input device controller306, an input device 308, display/audio drivers 310, display and audiooutput circuitry 312, a communication interface(s) 314, an antenna 316and a bus 318.

Referring now to FIG. 4, there is illustrated an example of a process400 for managing wind speed data in accordance with some embodiments ofthe disclosed subject matter. In FIG. 4, the example process 400 isillustrated by means of a block diagram wherein each block represents astep or steps of the process. In some embodiments, additional blocks canbe present in between and/or in series with and/or in parallel with theblocks illustrated and/or additional steps can be present between and/orin series with and/or in parallel with the steps described.

In some embodiments, the process 400 can be executed by any device orcombination of devices. For example, the process 400 can be executed atleast in part by one or more data servers (e.g. the data server 202 ofFIG. 2), one or more user devices (e.g., the user device 204 of FIG. 2),one or more wind stations (e.g., the wind stations 209 of FIG. 2 and/orwind station system 100 of FIG. 1), one or more certification servers(e.g., the certification server 206 of FIG. 2) and/or any other suitabledevice.

The wind speed data managing process 400 can begin at block 402 havingsteps of receiving an anemometer reading. In some embodiments, receivingstep 402 can receive an anemometer reading in any suitable format. Forexample, the step 402 can receive an electrical signal from theanemometer 104. As a more particular example, the electrical signal canbe an AC sine wave. In such a more particular example, the frequency ofthe AC sine wave can be proportional to the wind speed. In someembodiments, the anemometer reading can be a continuous reading. In someother embodiments, the anemometer reading can be an instantaneousreading or a plurality of instantaneous readings.

In some embodiments, the process 400 can include a block 404 havingsteps wherein the anemometer reading is converted to wind speed data. Insome embodiments, the steps of block 404 follow the steps of block 402.In some embodiments, the converting step 404 can convert the anemometerreading to wind speed data using any suitable technique or combinationof techniques and any suitable information. For example, if the receivedanemometer reading is an AC sine wave with a frequency proportional towind speed, the steps of block 404 can apply a predetermined multiplierto the frequency to calculate the wind speed.

In some embodiments, the process 400 can convert an anemometer reading(or a plurality of anemometer readings) over a predetermined period oftime to an average wind speed. For example, the process 400 can receive(e.g., in block 402) an anemometer reading or readings over a thirtysecond period, a one minute period or any other suitable amount of timeand convert (e.g., in block 404) the anemometer reading or readings overthat period to an average wind speed. Thus, in some embodiments, theblock 402 or 404 can further include steps of storing multipleanemometer readings received at intervals over a predetermined period oftime. In some embodiments, the block 404 can further include steps ofconverting multiple anemometer readings into an average wind speed.

In some embodiments, the steps of block 404 can include steps ofconverting an anemometer reading over a first predetermined period oftime to a maximum wind speed during a second, shorter, predeterminedtime period that is within the first predetermined period of time(referred to sometimes herein as a “peak gust”). For example, if thereceived anemometer reading in block 402 is an AC sine wave with afrequency proportional to wind speed, the block 404 can includedetermining the frequency of the wave over a ten-minute base period, andcalculating a moving average of the frequency over each three-secondperiod, and finding a maximum three-second average wind speed byapplying a predetermined multiplier to the maximum three-second movingaverage frequency. In other embodiments, any values for the firstpredetermined time period (i.e., “the base period”) and the secondpredetermined time period (i.e., “the moving average period”) can beused.

In some embodiments, the process 400 can include a block 406 havingsteps of determining whether the wind speed data is higher than apredetermined threshold. In some embodiments, the block 406 followsblock 404. For example, if the steps in block 404 convert the anemometerreading to a peak gust, the steps in block 406 can determine whether thepeak gust exceeds a predetermined threshold peak gust. As anotherexample, if the steps in block 404 convert the anemometer reading to anaverage wind speed, the steps in block 406 can determine whether theaverage wind speed exceeds a predetermined threshold wind speed.

In some embodiments of the process 400, in the event that the wind speedexceeds a predetermined threshold, the steps in block 406 can proceed(as denoted by arrow 408 in FIG. 4) to block 410 including steps ofsending an alert to be sent to a user device 204. In some embodiments,steps of block 410 can cause an alert to be sent to a user device 204using any technique or combination of techniques. For example, if theuser device 204 is a mobile phone, the steps of block 410 can cause atext message to be sent to the user device. As another example, if theuser device 204 is a personal computer, the steps of block 410 can sendan alert via e-mail. As yet another example, the steps of block 410 cancause an alert to be posted to a Web site.

In some embodiments, the steps of block 410 can send an alert to a userdevice 204 using any suitable communication network. For example, thesteps of block 410 can send an alert using the communication network 210shown in FIG. 2 and described in connection with the computer hardware200.

In some embodiments, the process 400 includes a block 412 having stepsof storing wind speed in local memory. In some embodiments, the steps ofblock 412 can either follow the steps of block 406 directly (as denotedby arrow 414 in FIG. 4) or via the steps of block 410 (as denoted byarrows 408 and 416 in FIG. 4). In some embodiments, any suitable localmemory can be used. For example, the steps of block 412 can store windspeed data in the local memory 130 of the storage device 118 as shown inFIG. 1 and described in connection with wind station system 100.

In some embodiments, the steps of block 412 can store wind speed data inlocal memory in any suitable format. For example, the steps of block 412can store the wind speed data in an XML format, JSON format, CSV format,and/or any other suitable data format.

In some embodiments, the steps of block 412 can store any amount of windspeed data in local memory. For example, in some embodiments the stepsof block 412 can store days, months, or years of wind speed data inlocal memory.

In some embodiments, the process 400 includes a block 418 having stepsof sending wind speed data to a data server. In some embodiments, thesteps of block 418 follow the steps of block 412. In some embodiments,the steps of block 412 can send wind speed data to a data server usingany suitable communication network. For example, the steps of block 412can send wind speed data to a data server 202 using the communicationnetwork 210 shown in FIG. 2 and described in connection with thehardware 200.

Referring now to FIG. 5, there is illustrated an example of a process500 for triggering wind speed payouts based on wind speed data inaccordance with some embodiments of the disclosed subject matter. InFIG. 5, the example process 500 is illustrated by means of a blockdiagram wherein each block represents a step or steps of the process. Insome embodiments, additional blocks can be present in between and/or inseries with and/or in parallel with the blocks illustrated and/oradditional steps can be present between and/or in series with and/or inparallel with the steps described.

In some embodiments, the triggering process 500 can be executed by anydevice or combination of devices. For example, the process 500 can beexecuted at least in part by one or more data servers (e.g. the dataserver 202 of FIG. 2), one or more user devices (e.g., the user device204 of FIG. 2), one or more wind stations (e.g., the wind station 209 ofFIG. 2 and/or wind station system 100 of FIG. 1), one or morecertification servers (e.g., the certification server 206 of FIG. 2),and/or any other suitable device.

In some embodiments, the trigging process 500 can begin at a block 502having steps of receiving an anemometer reading at a wind meter. In someembodiments, the steps of block 502 can receive an anemometer readingusing any suitable techniques or combination of techniques. For example,the steps of block 502 can receive an anemometer reading as describedabove for block 402 with reference to FIG. 4.

In some embodiments, the triggering process 500 includes a block 504having steps of converting an anemometer reading into wind speed data.In some embodiments, the steps of block 504 follow the steps of block502. In some embodiments, the steps of block 504 can convert ananemometer reading into wind speed data using any suitable techniques orcombination of techniques and any suitable information. For example, thesteps of block 504 can convert an anemometer reading into wind speeddata as described above for block 404 with reference to FIG. 4.

In some embodiments, the triggering process 500 includes a block 512having steps of storing wind speed data in a local memory of a windstation. In some embodiments, the steps of block 512 follow the steps ofblock 504. In some embodiments, the steps of block 512 can store windspeed data in a local memory of a wind station using any suitabletechniques or combination of techniques. For example, the steps of block512 can store wind speed data in the local memory of a wind station 209as described above for block 412 with reference to FIG. 4, or in thelocal memory 130 of a storage device 118 of a wind station system 100 asdescribed above with reference to FIG. 1.

In some embodiments, the triggering process 500 includes a block 513having steps of determining whether a data connection is available. Insome embodiments, the steps of block 513 can follow the steps of block512. The steps of block 513 can determine whether a data connection isavailable using any suitable techniques or combination of techniques andany suitable information. For example, the steps of block 513 candetermine whether a data connection is available by pinging a server,sending a test data packet, querying a server and/or any other suitabletechnique or combination of techniques.

If the steps of block 513 determine that a data connection is available,the process 500 can continue to block 518 (as denoted by arrow 514 inFIG. 5) having steps of sending wind speed data to a server. In someembodiments, the steps of block 518 can send wind speed data to a serverusing any suitable techniques or combination of techniques. For example,the steps of block 518 can send wind speed data to a server (e.g., thedata server 202 and/or certification server 206 of FIG. 2) as describedabove for block 418 with reference to FIG. 4. If the steps of block 513determine that a data connection is not available, the process 500 cancontinue by repeating an earlier part of the process (e.g., as denotedby arrow 516 in FIG. 5).

In some embodiments, the triggering process 500 includes a block 520having steps of receiving wind speed data at a data server (e.g., thedata server 202 of FIG. 2). In some embodiments, the steps of block 520follow the steps of block 518 (as denoted by arrow 519 in FIG. 5). Insome embodiments, the steps of block 520 can receive wind speed datausing any suitable techniques or combination of techniques. For example,the steps of block 520 can receive the wind speed data via acommunication network (e.g., the communication network 210 of FIG. 2).

In some embodiments, the triggering process 500 includes a block 522having steps of storing wind speed data. In some embodiments, the stepsof block 522 follow the steps of block 520. In some embodiments, thesteps of block 522 can store wind speed data using any suitabletechniques or combination of techniques. For example, the steps of block522 can store wind speed data on a memory and/or storage (e.g., thememory and/or storage 304 of FIG. 3).

In some embodiments, the triggering process 500 includes a block 524having steps of determining whether wind speed data should be sent forcertification. In some embodiments, the steps of block 524 can followthe steps of block 522. In some embodiments, the steps of block 524 candetermine whether wind speed data should be sent for certification usingany suitable techniques or combination of techniques and any suitableinformation. For example, the steps of block 524 can determine whetherwind speed data should be sent for certification based on whether thewind speed data is related to a named storm (e.g., a named hurricane ortyphoon). As a more particular example, if the wind speed data isgathered from a location and time period associated with a storm thathas been named by a weather organization (e.g., the National WeatherService), the steps of block 524 can determine that the wind speed datashould be sent for certification. As another example, the steps of block524 can determine whether wind speed data should be sent forcertification based on a threshold wind speed. As a more particularexample, if the wind speed data includes a wind speed that is higherthan a predetermined threshold wind speed, the steps of block 524 candetermine that the wind speed data should be sent for certification. Ifthe steps of block 524 determine that the wind speed data does not needto be certified, the process 500 can continue by repeating an earlierpart of the process (e.g., as denoted by arrow 519 in FIG. 5).

In some embodiments, the triggering process 500 includes a block 526having steps of generating a historical storm model. In someembodiments, the steps of block 526 can generate a historical stormmodel using any suitable technique or combination of techniques and anysuitable information.

In some embodiments, the steps of block 526 can generate a historicalstorm model using any suitable historical storm data. For example, thesteps of block 526 can use data cataloging the frequency and severity ofstorms along the United States coastline over a certain period. As amore particular example, the steps of block 526 can use a storm datasetthat records the time, date, latitude, longitude, maximum sustained windspeed, and central pressure for storms from the year 1900 through 2012.In other embodiments, the steps of block 526 can use a storm dataset forstorms from the year 1900 through the most recent year for which stormdata is available. In still other embodiments, the steps of block 526can use a storm dataset for storms from a predetermined first yearagreed-to under a contract through a predetermined final year agreed-tounder the contract.

In some embodiments, the steps of block 526 can further includesupplementing historical storm data by generating synthetic stormsand/or generating a historical storm model based at least in part on thesynthetic storms. For example, the process 500 and/or the steps of block526 can generate synthetic storms by utilizing the bogusing technique ofKurihara et al., “An Initialization Scheme of Hurricane Models by VortexSpecification,” Monthly Weather Review, vol. 2, July 1993, the contentof which is incorporated herein by reference.

In some embodiments, the triggering process 500 includes a block 528having steps of generating a wind speed damage model based on ahistorical storm model. In some embodiments, the steps of block 528 canfollow the steps of block 526, and the historical storm model can be thehistorical storm model generated by the steps of block 526. In someembodiments, the steps of block 528 can generate a wind speed damagemodel based on the historical storm model using any suitable techniquesor combination of techniques and any suitable information.

In some embodiments, the steps of block 528 can generate a wind speeddamage model by simulating wind gusts based on the historical stormmodel. For example, the steps of block 528 can simulate peak gusts inthe historical storm model and associate the simulated peak gusts withhistorical damage information.

In some embodiments, the triggering process 500 includes a block 530having steps of receiving wind speed data if the process determines(e.g., from the steps of block 524) that that wind speed data should besent for certification (i.e., as denoted by arrow 532 in FIG. 5). Insome embodiments, the steps of block 530 can receive wind speed datausing any suitable technique or combination of techniques. For example,the steps of block 530 can receive wind speed data via a communicationnetwork (e.g., the communication network 210 of FIG. 2) from a windstation, such as wind station system 100, as described above. As anotherexample, the steps of block 530 can receive wind speed data via acommunication network (e.g., the communication network 210 of FIG. 2)from a data server (e.g., the data server 202 of FIG. 2).

In some embodiments, the triggering process 500 includes a block 534having steps of generating a certification report for the received windspeed data based on the historical storm model, and/or the wind speeddamage model. In some embodiments, the steps of block 534 can follow thesteps of block 530. In some embodiments, the steps of block 534 cangenerate a certification report for the received wind speed data basedon the historical storm model (e.g., from block 526) and/or the windspeed damage model (e.g., from block 528) using any suitable techniqueor combination of techniques and any additional suitable information.For example, in some embodiments, the process 500 and the steps of block534 can generate a certification report by inputting (as denoted byarrow 536 in FIG. 5) the received wind speed data in addition toinformation related to buildings in an area related to the wind speeddata (e.g., construction class of the buildings, building height,building occupancy, year of construction, and/or floor area) into thewind speed damage model. As a more particular example, if the wind speeddata is within a predetermined number of standard deviations from a windspeed predicted by the model, the steps of block 534 can generate acertification report that certifies the wind speed data. As anotherexample, the steps of block 534 can generate a certification report bycomparing the received wind speed data (e.g., from block 530) with awind speed predicted by the historical storm model (e.g., from block526). As yet another example, the steps of block 534 can generate acertification report based on wind speed data received from a thirdparty.

In some embodiments, the triggering process 500 includes a block 538having steps of sending the certification report. In some embodiments,the steps of block 538 can follow the steps of block 534. In someembodiments, the steps of block 538 can send the certification reportusing any suitable techniques or combination of techniques. For example,the steps of block 538 can send the certification report to a dataserver (e.g., the data server 202 of FIG. 2) via a communication network(e.g., the communication network 210 of FIG. 2). The triggering process500 may further include a block 540 having steps of receiving thecertification report sent by the steps of block 538. In someembodiments, the steps of block 540 can receive the certification reportusing any suitable techniques or combination of techniques. For example,the steps of block 540 can receive the certification report from acommunication network (e.g., the communication network 210 of FIG. 2)using a data server (e.g., the data server 202 of FIG. 2).

In some embodiments, the triggering process 500 includes a block 542having steps of determining if a contract has been met. In someembodiments, the steps of block 542 can follow the steps of block 540.In some embodiments, the steps of block 542 can determine if a contracthas been met using any suitable techniques or combination of techniquesand/or any suitable information. For example, the steps of block 542 candetermine if a contract has been met based on the received certificationreport, e.g., the certification report received from block 540. Forexample, the steps of block 542 can determine that a wind speedcontained in wind speed data is greater than a threshold amountcontained in a contract and that the certification report certifies thatsuch a wind speed is correct, and accordingly determine that thecontract has been met. As another example, the steps of block 542 candetermine that a wind speed contained in wind speed data is greater thana threshold amount contained in a contract, and that the certificationreport does not certify that such a wind speed is correct, andaccordingly determine that the contract has not been met.

In some embodiments, the steps of block 542 can determine if a contracthas been met by submitting the wind speed data and certification reportfor manual review. For example, if the steps of block 542 determine thatwind speed data includes a wind speed that is higher than a thresholdwind speed contained in a contract, and that the certification reportcertifies that the wind speed data is correct, the steps of block 542can then submit the wind speed data and the certification report formanual review.

In some embodiments, the triggering process 500 includes a block 544having the steps of triggering a payout of a contract. In someembodiments, the steps of block 544 can follow the steps of block 542 ifthe steps of block 542 determined that the contract was met. In someembodiments, the steps of block 542 can trigger a payout of the contractusing any suitable technique or combination of techniques. For example,the steps of block 542 can trigger a payout of the contract by sendinginformation to a contract payout server (e.g., the contract payoutserver 208 of FIG. 2). As another example, the steps of block 542 cantrigger a payout by processing an electronic transaction such as a bankdeposit, an electronic funds transfer, a direct deposit, sending adigital currency and/or any other suitable electronic transaction.

In some embodiments, at least some of the above-described blocks and/orsteps of the processes of FIGS. 4 and 5 can be executed or performed inany order or sequence not limited to the order and sequence shown in anddescribed in connection with the figures. Also, some of the above blocksand/or steps of FIGS. 4 and 5 can be executed or performed substantiallysimultaneously where appropriate or in parallel to reduce latency andprocessing times. Additionally or alternatively, some of the abovedescribed blocks and/or steps of the processes of FIGS. 4 and 5 can beomitted.

In some embodiments, any suitable computer readable media can be usedfor storing instructions for performing the functions and/or processesherein. For example, in some embodiments, computer readable media can betransitory or non-transitory. For example, nontransitory computerreadable media can include media such as magnetic media (such as harddisks, floppy disks, and/or any other suitable magnetic media), opticalmedia (such as compact discs, digital video discs, Blu-ray discs, and/orany other suitable optical media), semiconductor media (such as flashmemory, electrically programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), and/or any othersuitable semiconductor media), any suitable media that is not fleetingor devoid of any semblance of permanence during transmission, and/or anysuitable tangible media. As another example, transitory computerreadable media can include signals on networks, in wires, conductors,optical fibers, circuits, any suitable media that is fleeting and devoidof any semblance of permanence during transmission, and/or any suitableintangible media.

In accordance with additional aspects and embodiments of the disclosedsubject matter, mechanisms (which can include methods, systems, andmedia) for managing seismic data are described herein.

Referring now FIG. 6, there is illustrated an example of a seismicstation system 600 for managing seismic data in accordance with someembodiments of the disclosed subject matter. In some embodiments, theseismic station system 600 is disposed at a geographic location ofinterest and manages seismic data for earthquakes and other seismicevents occurring at that geographic location. In some embodiments, aparticular seismic station system 600 can manage seismic data for itsown geographic location (also known as “local seismic data”) and canalso receive seismic signals relevant to other seismic stations, i.e.,at different geographic locations (also known as “remote seismicstations”), and produce seismic data for the remote seismic signals(also known as “remote seismic data”). The remote seismic data can bemanaged by the particular seismic station system 600 for quality controlpurposes and/or to certify the seismic data received from the remoteseismic stations. As shown, in some embodiments, the seismic system 600can include a seismometer 602, an accelerometer 604, a data processor606 and a memory 608. Some embodiments of system 600 can include onlyone or more seismometers 602, other embodiment can include only one ormore accelerometers 604, and still other embodiments can include bothseismometer(s) and accelerometer(s). Seismic waves (also known asseismic readings) at the geographic location are detected by theseismometer 602, converted into electrical signals and sent to the dataprocessor 606. Ground accelerations (also known as accelerationreadings) at the geographic location are detected by the accelerometer604, converted into electrical signals and sent to the data processor606. In various embodiments, the accelerometer 604 can be a single axisaccelerometer or a multi-axis accelerometer, and in particular, it canbe a three-axis accelerometer for detecting axial accelerations alongthree separate axes or a six-axis accelerometer for detecting both axialand rotational accelerations along three separate axes. In variousembodiments, the accelerometer 604 can be a piezoelectric accelerometer,a piezoresistive accelerometer or a capacitive accelerometer. In someembodiments, the accelerometer 604 can be a micro electro-mechanicalsystems (“MEMS”) device of the type having a cantilever beam with aproof mass (also known as seismic mass). In other embodiments, theaccelerometer 604 can be a MEMS thermal type using a heated fluid insidea dome to produce a thermal bubble that acts as the proof mass.

The data processor 606 receives the electrical signals from theseismometer 602 and accelerometer 604 and converts the signals intoseismic data that can be recorded in the memory 608. In some embodimentsof the system 600, the seismic data can be digital data and the memory608 can be a digital data storage device including, but not limited to,a hard disk drive (“HDD”) or a solid state drive (“SSD”). In otherembodiments of the system 600, the seismic data can be digital data andthe memory 608 can be digital data storage media including, but notlimited to, a solid-state non-volatile memory device, a flash memorycard, a Secure Digital card or a Compact Flash card. In still otherembodiments of the system 600, the seismic data can be analog data andthe memory 608 can be an analog data storage device or analog datastorage media.

Referring still to FIG. 6, in some embodiments of the system 600, one ormore of the seismometer 602, accelerometer 604, data processor 606 andmemory 608 can be disposed inside a secure housing 610 disposed at theselected geographic location of interest. In the illustrated embodiment,the secure housing 610 includes a main housing 612 disposed at or belowgrade level 613 and a housing lid or door 614 that can enclose therelevant system components within the main housing. In otherembodiments, the housing 610 may be disposed above grade, e.g., attachedto a foundation, wall or other structural member of a building. The mainhousing 612 and the housing lid 614 can be formed of damage-resistantmaterials such as concrete or steel to protect the system componentsduring an earthquake or during a structure collapse or fire that mayaccompany or follow the quake.

To prevent or detect tampering with the system 600, the housing 610 canfurther be equipped with a security device 616 that can lock the housingand/or can detect opening of the housing lid 614. The security device616 can send electrical signals to the data processor 606 to indicateopening of the housing lid 614, and the data processor can convert thesignals from the security device into security data that can be sent tothe memory 608 for storage.

The system 600 can further include a battery 618 to provide electricalpower for operation of the seismometer 602, accelerometer 604, dataprocessor 606 and/or memory 608. In some embodiments, the battery 618can be disposed within the housing 610 to provide power to the internalsystem components in case external connections 620 to the housing arecut or disabled. For example, if a first small earthquake event occursthat cuts off external power (e.g., mains power) to the system 600, thebattery 618 can continue to power the measuring instruments 602 and 604,processor 606 and memory 608 such that a subsequent larger earthquakeevent occurring while the mains power is out can be detected andrecorded.

The seismic system 600 can further include a computing device 622operably connected to the data processor 606 and memory 608. In theillustrated embodiment, the computing device 622 is located externallyto the housing 610 and connected to equipment within the housing viaconnection 620, which can include electrical or fiber optic data cablesand/or electrical power cables. In other embodiments, the computingdevice 622 can be located inside the housing 610. In some embodiments,the connection 620 can comprise a wireless data communication linkincluding, but not limited to, WiFi (i.e., IEEE 802.11 series),Bluetooth (i.e., IEEE 802.15 series and Bluetooth SIG series) or otherlocal area wireless technology. The computing device 622 can include adisplay device 624 to display information regarding detected seismicevents, the status of the system and system components, messages fromthe other elements of the system, etc. In the illustrated embodiment,the computing device 622 is separate from the data processor 606 and thememory 608; however, in some other embodiments, the data processorand/or the memory may be components of the computing device 622. Instill other embodiments, the computing device 622 can comprise asecondary or redundant data processor to augment or “back up” theprimary data processor 606 and/or a secondary or redundant memory toaugment or “back up” the primary data memory 608.

The computing device 622 can communicate with a communication network210, for example, either the same network or a network similar to thatdescribed in connection with the wind station system 100 of FIGS. 1 and2. The communication network 210 can be any suitable combination of oneor more wired and/or wireless networks in some embodiments. For example,the communication network 210 can include anyone or more of theInternet, an intranet, a wide-area network (WAN), a local-area network(LAN), a wireless network, a digital subscriber line (DSL) network, aframe relay network, an asynchronous transfer mode (ATM) network, avirtual private network (VPN), and/or any other suitable communicationnetwork. The computing device 622 can be connected to the communicationnetwork 210 by one or more wireless communication links 626 and/or oneor more hard wired communication links 628.

Referring now again to FIG. 3, the computer hardware 300 illustrated inconnection with the computing device 108 of the wind station system 100or wind station 209 can similarly be implemented as the computing device622 of the seismic station system 600. The various components andoperations of the computer hardware 300 described in connection withcomputing device 108 can be applied in analogous fashion to thecomputing device 622, and therefore will not be repeated.

Referring now to FIG. 7, there is illustrated one example of systemhardware 700 for managing seismic data that can be used in accordancewith some embodiments of the disclosed subject matter. As illustrated,the system hardware 700 can include one or more: data servers 702, userdevices 704, certification servers 706, contract payout servers 708 andseismic stations 709 outfitted with computing devices 622.

In some embodiments, the seismic station 709 can be any suitable seismicstation configured with a computing device 622. For example, as shown inFIG. 6, the seismic station 709 can be the seismic station system 600disposed at a particular geographic location.

In some embodiments, the data server 702 can be any suitable server forstoring data and/or delivering the data to a user device 704. In someembodiments, the data stored by the data server 702 and/or delivered tothe user device 704 can be implemented as digital data in any digitaldata format. For example, the data server 702 can be a server thatdelivers data to a user device 704 and/or receives seismic data from aseismic station 709 via a communication network 210. In someembodiments, the data server 702 can include a server computing device,a server communication interface operatively connected to thecommunication network 210 to receive respective seismic data from one ormore seismic stations 709 and operatively connected to the servercomputing device to provide the received respective seismic data to theserver computing device and a server memory disposed at the respectivedata server location and operatively connected to the server computingdevice for storing the received respective seismic data. Data storedand/or delivered by the data server 702 can be any suitable data, suchas seismic wave data relating to amplitude, frequency, direction,occurrence time or duration of seismic wave readings at the geographiclocation of interest, seismic magnitude or intensity readings at thegeographical location of interest (e.g., derived by the data processor606 from the seismic readings or data), acceleration data relating toamplitude, frequency, direction, occurrence time or duration of groundacceleration at the geographic location of interest, ground velocitydata relating to amplitude, frequency, direction, occurrence time orduration at the geographic location of interest (e.g., derived by thedata processor 606 from the acceleration readings), historical seismicevent data, contract data, contract payout data and/or any othersuitable data. Data can be recorded and uploaded to the data server 702by any suitable entity (e.g., a seismic station computing device 622).In some embodiments, the data server 702 can be disposed at a geographiclocation that is remote from (i.e., geographically distant from) theseismic station system 600, whereas in other embodiments, the dataserver can be disposed at the same geographic location as the seismicstation system. In some embodiments having more than one seismic stationsystem 600, each respective seismic station system can be disposed at adifferent respective seismic station location, and the data server 702can be disposed at a data server location that is remote from at leastone of the respective seismic station locations. In some embodimentshaving more than one seismic station system 600 and more than one dataserver 702, each respective seismic station system can be disposed at adifferent respective seismic station location, and each respective dataserver can be disposed at a different respective data server location,wherein the respective seismic station locations and data serverlocations are all geographically remote from one another. In some otherembodiments, the data server 702 can be omitted.

As previously described, the communication network 210 can be anysuitable combination of one or more wired and/or wireless networks insome embodiments. For example, the communication network 210 can includeanyone or more of the Internet, an intranet, a wide-area network (WAN),a local-area network (LAN), a wireless network, a digital subscriberline (DSL) network, a frame relay network, an asynchronous transfer mode(ATM) network, a virtual private network (VPN), and/or any othersuitable communication network. The user device 704 can be connected byone or more communications links 212 to the communication network 210,which can be linked via one or more communications links to the dataserver 702, and/or seismic stations 709. The communications links 212can be any communications links suitable for communicating data amongthe user device 704, data server 702 and seismic stations 709, such asnetwork links, dial-up links, wireless links, hard-wired links, anyother suitable communications links, or any suitable combination of suchlinks. In some embodiments, the data communicated across thecommunication network 210 and/or communication links 212 can beimplemented as digital data in any digital data format.

The user device 704 can include any one or more user devices suitablefor requesting data, searching for data, viewing data, retransmittingdata, manipulating data, receiving a user input and/or any othersuitable functions. For example, in some embodiments, the user device704 can be implemented as a mobile device, such as a mobile phone, atablet computer, a laptop computer and/or any other suitable mobiledevice. As another example, in some embodiments, the user device 704 canbe implemented as a non-mobile device such as a desktop computer and/orany other suitable non-mobile device. In some embodiments, the userdevice 704 can be disposed at a geographic location that is remote from(i.e., geographically distant from) the seismic station system 600and/or the data server 702, whereas in other embodiments, the userdevice can be disposed at the same geographic location as the seismicstation system and/or the data server.

In some embodiments, the contract payout server 708 can be any suitableserver for causing a contract to be paid out based on seismic data. Forexample, the contract payout server 708 can be a server that receivesseismic data from a data server 702 via a communication network 210,and/or determines whether a contract should be paid out based on seismicdata and/or causes a third party server 714 to payout a contract bycommunicating with the third party server over a communication network210. The storage of the seismic data and other information, programs,data and/or other suitable information on the contract payout server 708can be implemented as digital data in any digital data format. In someembodiments, the contract payout server 708 can be implemented byhardware analogous to that previously described in connection with FIG.3. In some embodiments, the payout server 708 can include a payoutserver computing device or hardware processor 302, a payout servercommunication interface 316 operatively connected to the communicationnetwork 210 to receive respective certification reports from one or morecertification servers 706 and operatively connected via a data bus 318to the payout server computing device to provide the received respectivecertification reports to the payout server computing device, and/or apayout server memory 304 operatively connected via the data bus to thepayout server computing device for storing the received respectivecertification reports. In some embodiments, the payout server computingdevice 302 can determine if a received respective certification reportsatisfied the terms of an associated contract, and if so, the payoutserver can trigger a payout at another location by communicating overthe communication network 210. In some embodiments, the contract payoutserver 708 can be disposed at a geographic location that is remote from(i.e., geographically distant from) the seismic station system 600, thedata server 702 and/or the user device 704, whereas in otherembodiments, the contract payout server can be disposed at the samegeographic location as the seismic station system, the data serverand/or the user device.

In some embodiments, the certification server 706 can be any suitableserver for certifying seismic data. For example, the certificationserver 706 can be a server that receives seismic data from a data server702 via a communication network 210, and/or stores historical seismicdata and/or determines whether seismic data is accurate. The storage ofthe seismic data and other information, programs, data and/or othersuitable information on the certification server 706 can be implementedas digital data in any digital data format. In some embodiments, thecertification server 706 can be implemented by hardware analogous tothat previously described in connection with FIG. 3. In someembodiments, the certification server 706 can include a certificationserver computing device or hardware processor 302, a certificationserver communication interface 316 operatively connected to thecommunication network 210 to receive respective seismic data from one ormore data servers 702 and operatively connected via a data bus 318 tothe certification server computing device to provide the receivedrespective seismic data to the certification server computing device,and/or a certification server memory 304 operatively connected via thedata bus to the certification server computing device for storing thereceived respective seismic data. In some embodiments, the certificationserver computing device 302 can generate a data model, for example ahistorical earthquake/seismic event model or a earthquake/seismic eventdamage model, and the generated data model can be transmitted by thecertification server communication interface 314 to another location onthe communication network 210. In some embodiments, the certificationserver computing device 302 can generate a certification report based onthe received seismic data and the generated data model, and thecertification report can be transmitted by the certification servercommunication interface 314 to another location on the communicationnetwork 210. In some embodiments, the certification server 706 can bedisposed at a geographic location that is remote from (i.e.,geographically distant from) the seismic station system 600, the dataserver 702, the user device 704 and/or the contract payout server 708,whereas in other embodiments, the contract payout server can be disposedat the same geographic location as the seismic station system, the dataserver, the user device and/or the contract payout server.

Although the data server 702 and the user device 704 are illustrated asseparate devices in FIG. 7, the functions performed by the data serverand the user device can be performed using any suitable number ofdevices in some embodiments. For example, in some embodiments, thefunctions performed by either the data server 702 or the user device 704can be performed on a single device. As another example, in someembodiments, multiple devices can be used to implement the functionsperformed by the data server 702 and the user device 704.

Although the data server 702, certification server 706, and the contractpayout server 708 are illustrated as separate devices in FIG. 7, thefunctions performed by the data server, certification server and thecontract payout server can be performed using any suitable number ofdevices in some embodiments. For example, in some embodiments, thefunctions performed by either the data server 702, the certificationserver 706, or the contract payout server 708 can be performed on asingle device. As another example, in some embodiments, multiple devicescan be used to implement the functions performed by the data server 702,the certification server 706 and the contract payout server 708.

Although only two seismic stations 709, one certification server 706,one contract payout server 708, one data server 702, one user device 704and one third-party server 714 are shown in FIG. 7 to avoidover-complicating the figure, any suitable number and/or any suitabletypes of seismic stations, data servers, user devices and third-partyservers can be used in some embodiments.

The data server 702, the user device 704, and the seismic stationcomputing devices 622 can be implemented using any suitable hardware insome embodiments. For example, in some embodiments, the data server 702,the user device 704 and the seismic station computing devices 622 can beimplemented using any suitable general purpose computer or specialpurpose computer. For example, the seismic station computing device 622may be implemented using a general purpose computer or a special purposecomputer. Any such general purpose computer or special purpose computercan include any suitable hardware. For example, referring again to FIG.3, as illustrated in example computer hardware 300, such hardware caninclude a hardware processor 302, a memory and/or storage 304, an inputdevice controller 306, an input device 308, display/audio drivers 310,display and audio output circuitry 312, a communication interface(s)314, an antenna 316 and a bus 318.

Referring now to FIG. 8, there is illustrated an example of a process800 for managing seismic data in accordance with some furtherembodiments of the disclosed subject matter. In FIG. 8, the exampleprocess 800 is illustrated by means of a block diagram wherein eachblock represents a step or steps of the process. In some embodiments,additional blocks can be present in between and/or in series with and/orin parallel with the blocks illustrated and/or additional steps can bepresent between and/or in series with and/or in parallel with the stepsdescribed.

In some embodiments, the process 800 can be executed by any device orcombination of devices. For example, the process 800 can be executed atleast in part by one or more data servers (e.g. the data server 702 ofFIG. 7), one or more user devices (e.g., the user device 704 of FIG. 7),one or more seismic stations (e.g., the seismic stations 709 of FIG. 7and/or seismic station system 600 of FIG. 6), one or more certificationservers (e.g., the certification server 706 of FIG. 7) and/or any othersuitable device.

The seismic data managing process 800 can begin at block 801 havingsteps wherein a seismic station 709 having a seismometer and/oraccelerometer is installed at the geographic location of interest. Thisstep allows the process 800 to utilize seismic data obtained directly atthe geographic location of interest rather than relying only onisoseismal maps or estimates based on seismic measurements at othergeographic locations. The block 801 can further have steps wherein theseismic station 709 is connected to the communication network 210 tosend seismic data or other communications to various servers 702, 706,708 and 714, devices 704 and other seismic stations 709 connected to thenetwork. When multiple seismic stations 709 are connected together viathe communication network 210, the process 800 can utilize seismic datareceived from seismic stations at other geographic locations (i.e.,remote from the location of interest) to augment and supplement seismicdata obtained from the seismic station directly at the geographiclocation of interest. For example, remote seismic data received fromanother seismic station 709 at a remote geographic location can be used,in whole or in part, to determine if recorded seismic data from a firstseismic station at the location of interest is accurate, e.g., as stepsof a data certification process.

In some embodiments, the process 800 can include block 802 having stepsof receiving a seismic signal from a seismometer. In some embodiments,receiving step 802 can receive a seismic signal in any suitable format.For example, the step 802 can receive an electrical signal from theseismometer 602 at the seismic station 709. The electrical signalreceived from the seismometer 602 can be an analog signal or a digitalsignal. In some embodiments, the seismic signals can correspond toseismic P-waves, S-waves, and/or the frequency and/or the magnitude ofsuch seismic waves detected by the seismometer 602. In some embodiments,the seismometer signal can be a continuous reading. In some otherembodiments, the seismometer signal can be an instantaneous reading or aplurality of instantaneous readings.

In some embodiments, the process 800 can include block 804 having stepsof receiving an acceleration signal from an accelerometer. In someembodiments, receiving step 804 can receive an acceleration signal inany suitable format. For example, the step 804 can receive an electricalsignal from the accelerometer 604 at the seismic station 709. Theelectrical signal received from the accelerometer 604 can be an analogsignal or a digital signal. In some embodiments, the acceleration signalreceived from the accelerometer 604 can correspond to axial and/orrotational accelerations around one or more axes, and/or the frequencyand/or the magnitude of such accelerations. In other embodiments, theacceleration signals received from the accelerometer 604 can correspondto axial and/or rotational accelerations of the ground or a structure atthe geographic location of interest, and/or the frequency and/or themagnitude of such accelerations. In some embodiments, the accelerationsignal can be a continuous reading. In some other embodiments, theacceleration signal can be an instantaneous reading or a plurality ofinstantaneous readings.

In some embodiments of the process 800, the steps of block 802 areabsent and only the steps of block 804 are present. In other embodimentsof the process 800, the steps of block 804 are absent and only the stepsof block 802 are present. In still other embodiments of the process 800,the steps of both block 802 and 804 are present. When the steps of bothblocks 802 and 804 are present, the steps of block 802 can be performedbefore the steps of block 804, the steps of block 804 can be performedbefore the steps of block 802, or the steps can be performedsimultaneously.

In some embodiments, the process 800 can include a block 806 havingsteps wherein the received seismic signal and/or the receivedacceleration signal are converted to seismic data. In the illustratedembodiment, the steps of block 806 follow the steps of both blocks 802and 804. In other embodiments, the steps of block 806 can be dividedinto analogous blocks 806′ and 806″, wherein the steps of block 806′(converting seismic signals to first seismic data) can follow the stepsof block 802 and the steps of block 806″ (converting accelerationsignals to second seismic data) can follow the steps of block 804. Insome embodiments, the converting step 806 can convert the seismic signaland/or the acceleration signal to seismic data using any suitabletechnique or combination of techniques and any suitable information. Insome embodiments, the process 800 can covert a first type of seismicsignal, e.g., ground accelerations signals, into a second type ofseismic signal or seismic data, e.g., ground velocity signals or groundvelocity data, using known relationships between acceleration andvelocity.

In some embodiments, the process 800 can convert a seismic signal (or aplurality of seismic signals) received, e.g., from the seismometer 602,over a predetermined period of time to an average seismic signal. Forexample, the process 800 can receive (e.g., in block 802) a seismicsignal or signals relating to seismic wave frequency over a thirtysecond period, a one minute period or any other suitable amount of timeand convert (e.g., in block 806) the seismic signals or signals overthat period to an average seismic wave frequency value. Similar stepscan be used to determine an average value for seismic signalscorresponding to other effects of seismic waves including, but notlimited to, a magnitude or intensity of a seismic event. In otherembodiments, the process 800 can convert an acceleration signal (or aplurality of acceleration signals) received, e.g., from theaccelerometer 604, over a predetermined period of time to an averageacceleration signal. For another example, the process 800 can receive(e.g., in block 804) an acceleration signal or signals over a thirtysecond period, a one minute period or any other suitable amount of timeand convert (e.g., in block 806) the acceleration signals or signalsover that period to an average acceleration value. Similar steps can beused to determine an average value for other quantities that can bederived from acceleration signals including, but not limited to, averagevelocity values. Thus, in some embodiments, the blocks 802 or 804 canfurther include steps of storing multiple seismic or accelerationsignals received at intervals over a predetermined period of time.

In some embodiments, the steps of block 806 can include steps ofconverting seismic signals over a first predetermined period of time toa maximum seismic value during a second, shorter, predetermined timeperiod that is within the first predetermined period of time (referredto sometimes herein as a “peak” seismic value). For example, if thereceived seismic signals in block 802 are signals proportional toseismic intensity, the block 806 can include determining the seismicintensity over a ten-minute base period, and calculating a movingaverage of the seismic intensity over each three-second period, andfinding a maximum three-second average seismic intensity by applying apredetermined multiplier to the maximum three-second moving averageseismic intensity. In other embodiments, any values for the firstpredetermined time period (i.e., “the base period”) and the secondpredetermined time period (i.e., “the moving average period”) can beused.

Similarly, in other embodiments, the steps of block 806 can includesteps of converting acceleration signals over a first predeterminedperiod of time to a maximum acceleration value during a second, shorter,predetermined time period that is within the first predetermined periodof time (referred to sometimes herein as a “peak” acceleration value).For example, if the received acceleration signals in block 804 aresignals proportional to ground acceleration, the block 806 can includedetermining the ground acceleration over a ten-minute base period, andcalculating a moving average of the ground acceleration over eachthree-second period, and finding a maximum three-second average groundacceleration by applying a predetermined multiplier to the maximumthree-second moving average ground acceleration. In other embodiments,any values for the first predetermined time period (i.e., “the baseperiod”) and the second predetermined time period (i.e., “the movingaverage period”) can be used.

In some embodiments, the process 800 can include a block 808 havingsteps of determining whether the value corresponding to the receivedseismic data (i.e., the “measured value”) is higher than a predeterminedthreshold value. In some embodiments, the received seismic data may bedirect measured values, e.g., seismic intensity values or groundacceleration values. In other embodiments, the received seismic data maybe calculated seismic values derived from the direct measured values,e.g., ground acceleration values, and/or peak or average values of anysuch received data. In some embodiments, the block 808 follows block806. For example, if the steps in block 806 convert the seismic signalsto a peak measured seismic intensity value, the steps in block 808 candetermine whether the peak measured seismic intensity value exceeds apredetermined threshold peak seismic intensity value. As anotherexample, if the steps in block 806 convert the seismic signals to ameasured average seismic intensity value, the steps in block 808 candetermine whether the measured average seismic intensity value exceeds apredetermined threshold average seismic intensity value.

Similarly, in some other embodiments, the process 800 can include ablock 808 having steps of determining whether the value corresponding tothe received acceleration data (i.e., the “measured value”) is higherthan a predetermined threshold value. In some embodiments, the block 808follows block 806. For example, if the steps in block 806 convert theacceleration signals to a peak measured acceleration value, the steps inblock 808 can determine whether the peak measured acceleration valueexceeds a predetermined threshold peak acceleration value. As anotherexample, if the steps in block 806 convert the acceleration signals to ameasured average acceleration value, the steps in block 808 candetermine whether the measured average acceleration value exceeds apredetermined threshold average acceleration value.

Further, in yet other embodiments, the process 800 can include a block808 having steps of determining whether the value corresponding to thereceived velocity data (i.e., the “measured value”) is higher than apredetermined threshold value. In some embodiments, the block 808follows block 806. For example, if the steps in block 806 convert thevelocity signals (or the original acceleration signals) to a peakmeasured velocity value, the steps in block 808 can determine whetherthe peak measured velocity value exceeds a predetermined threshold peakvelocity value. As another example, if the steps in block 806 convertthe velocity signals (or the original acceleration signals) to ameasured average velocity value, the steps in block 808 can determinewhether the measured average velocity value exceeds a predeterminedthreshold average velocity value.

In some embodiments of the process 800, in the event that the seismicvalue (e.g., the measured seismic value, measured average seismic valueor measured peak seismic value) or acceleration value (e.g., themeasured acceleration value, measured average acceleration value ormeasured peak acceleration value) or velocity value (e.g., the measuredvelocity value, measured average velocity value or peak measuredvelocity value) exceeds a predetermined threshold value, the steps inblock 808 can proceed (as denoted by arrow 810 in FIG. 8) to block 812including steps of sending an alert to be sent to a user device 704. Insome embodiments, steps of block 812 can cause an alert to be sent to auser device 704 using any technique or combination of techniques. Forexample, if the user device 704 is a mobile phone, the steps of block812 can cause a text message to be sent to the user device. As anotherexample, if the user device 704 is a personal computer, the steps ofblock 812 can send an alert via e-mail. As yet another example, thesteps of block 812 can cause an alert to be posted to a Web site.

In some embodiments, the steps of block 812 can send an alert to a userdevice 704 using any suitable communication network. For example, thesteps of block 812 can send an alert using the communication network 210shown in FIGS. 6 and 7 and described in connection with the hardware 600and 700.

In some embodiments, the process 800 includes a block 816 having stepsof storing seismic data (including acceleration data and/or velocitydata, if applicable) in local memory. In some embodiments, the steps ofblock 816 can either follow the steps of block 808 directly (as denotedby arrow 814 in FIG. 8) or via the steps of block 812 (as denoted byarrows 810 and 818 in FIG. 8). In some embodiments, any suitable localmemory can be used. For example, the steps of block 816 can storeseismic data in the local memory 608 as shown in FIG. 6 and described inconnection with seismic station system 600.

In some embodiments, the steps of block 816 can store seismic data inlocal memory (e.g., memory 608) in any suitable format. For example, thesteps of block 816 can store the wind speed data in an XML format, JSONformat, CSV format, and/or any other suitable data format.

In some embodiments, the steps of block 816 can store various quantitiesof seismic data in local memory. For example, in some embodiments thesteps of block 816 can store days, months, or years of seismic data inlocal memory. In some embodiments, if the amount of stored seismic datareaches the capacity of a local memory (e.g., memory 608), a processor(e.g., processor 606) can continue to store new seismic data byoverwriting the oldest previously stored seismic data. In otherembodiments, if the amount of seismic data stored in the local memoryreaches a predetermined fraction of the total capacity of the localmemory, a processor can send a message to a user device 704 or otherdevice over the communication network 210.

In some embodiments, the process 800 includes a block 820 having stepsof sending seismic data to a data server. In some embodiments, the stepsof block 820 follow the steps of block 816. In some embodiments, thesteps of block 820 can send seismic data to a data server using anysuitable communication network. For example, the steps of block 820 cansend seismic data to a data server 702 using the communication network210 shown in FIGS. 6 and 7 and described in connection with the hardware600 and 700.

Referring now to FIG. 9, there is illustrated an example of a process900 for triggering seismic event payouts based on seismic data inaccordance with some embodiments of the disclosed subject matter. InFIG. 9, the example process 900 is illustrated by means of a blockdiagram wherein each block represents a step or steps of the process. Insome embodiments, additional blocks can be present in between and/or inseries with and/or in parallel with the blocks illustrated and/oradditional steps can be present between and/or in series with and/or inparallel with the steps described.

In some embodiments, the triggering process 900 can be executed by anydevice or combination of devices. For example, the process 900 can beexecuted at least in part by one or more data servers (e.g. the dataserver 702 of FIG. 7), one or more user devices (e.g., the user device704 of FIG. 7), one or more seismic stations (e.g., the seismic station709 of FIG. 7 and/or seismic station system 600 of FIG. 6), one or morecertification servers (e.g., the certification server 706 of FIG. 7),and/or any other suitable device.

In some embodiments, the trigging process 900 can begin at a block 902having steps of receiving a seismic signal or an acceleration signalindicative of a seismic event at a seismic station 709. In someembodiments, the steps of block 902 can receive the seismic signal orthe acceleration signal using any suitable techniques or combination oftechniques. For example, the steps of block 902 can receive the seismicsignal or the acceleration signal as described above for block 802and/or block 804, with reference to FIG. 8.

In some embodiments, the triggering process 900 includes a block 904having steps of converting an seismic signal and/or an accelerationsignal into seismic data. In some embodiments, the steps of block 904follow the steps of block 902. In some embodiments, the steps of block904 can convert a seismic signal into seismic data using any suitabletechniques or combination of techniques and any suitable information.For example, the steps of block 904 can convert a seismometer oraccelerometer signal into seismic data as described above for block 806with reference to FIG. 8.

In some embodiments, the triggering process 900 includes a block 912having steps of storing seismic data in a local memory of a seismicstation 709. In some embodiments, the steps of block 912 follow thesteps of block 904. In some embodiments, the steps of block 912 canstore seismic data in a local memory of a seismic station 709 using anysuitable techniques or combination of techniques. For example, the stepsof block 912 can store seismic data in the local memory of a seismicstation 709 as described above for block 816 with reference to FIG. 8,or in the local memory 608 of a seismic station system 600 as describedabove with reference to FIG. 6.

In some embodiments, the triggering process 900 includes a block 913having steps of determining whether a data connection is available. Insome embodiments, the steps of block 913 can follow the steps of block912. The steps of block 913 can determine whether a data connection isavailable using any suitable techniques or combination of techniques andany suitable information. For example, the steps of block 913 candetermine whether a data connection is available by pinging a server,sending a test data packet, querying a server and/or any other suitabletechnique or combination of techniques.

If the steps of block 913 determine that a data connection is available,the process 900 can continue to block 918 (as denoted by arrow 914 inFIG. 9) having steps of sending seismic data to a server (e.g., 702 or706). In some embodiments, the steps of block 918 can send seismic datato a server (e.g., 702 or 706) using any suitable techniques orcombination of techniques. For example, the steps of block 918 can sendseismic data to a server (e.g., the data server 702 and/or certificationserver 706 of FIG. 7) as described above for block 820 with reference toFIG. 8. If the steps of block 913 determine that a data connection isnot available, the process 900 can continue by repeating an earlier partof the process (e.g., as denoted by arrow 916 in FIG. 9).

In some embodiments, the triggering process 900 includes a block 920having steps of receiving seismic data at a data server (e.g., the dataserver 702 of FIG. 7). In some embodiments, the steps of block 920follow the steps of block 918 (as denoted by arrow 919 in FIG. 9). Insome embodiments, the steps of block 920 can receive seismic data usingany suitable techniques or combination of techniques. For example, thesteps of block 920 can receive the seismic data via a communicationnetwork (e.g., the communication network 210 of FIGS. 6 and 7).

In some embodiments, the triggering process 900 includes a block 922having steps of storing seismic data. In some embodiments, the steps ofblock 922 follow the steps of block 920. In some embodiments, the stepsof block 922 can store seismic data using any suitable techniques orcombination of techniques. For example, the steps of block 922 can storeseismic data on a memory and/or storage (e.g., the memory and/or storage304 of FIG. 3).

In some embodiments, the triggering process 900 includes a block 924having steps of determining whether seismic data should be sent forcertification. In some embodiments, the steps of block 924 can followthe steps of block 922. In some embodiments, the steps of block 924 candetermine whether seismic data should be sent for certification usingany suitable techniques or combination of techniques and any suitableinformation. For example, the steps of block 924 can determine whetherseismic data should be sent for certification based on whether theseismic data is related to a well-known seismic event (e.g., anationally publicized seismic event). As a more particular example, ifthe seismic data is gathered from a location and time period associatedwith an earthquake or seismic event reported by a national seismic orgeological organization (e.g., the United Stated Geological Survey“USGS”) or national emergency organization (e.g., the Federal EmergencyManagement Agency “FEMA”), the steps of block 924 can determine that theseismic data should be sent for certification. As another example, thesteps of block 924 can determine whether seismic data should be sent forcertification based on a threshold seismic value. As a more particularexample, if the seismic data includes a seismic intensity value that ishigher than a predetermined threshold seismic intensity value, the stepsof block 924 can determine that the seismic data should be sent forcertification. Similarly, if the seismic data includes a groundacceleration value that is higher than a predetermined threshold groundacceleration value, the steps of block 924 can determine that theseismic data should be sent for certification. Similarly, if the seismicdata includes a ground velocity value that is higher than apredetermined threshold ground velocity value, the steps of block 924can determine that the seismic data should be sent for certification. Ifthe steps of block 924 determine that the seismic data does not need tobe certified, the process 900 can continue by repeating an earlier partof the process (e.g., as denoted by arrow 919 in FIG. 9).

In some embodiments, the triggering process 900 includes a block 926having steps of generating a historical earthquake or seismic eventmodel. In some embodiments, the steps of block 926 can generate ahistorical earthquake or seismic event model using any suitabletechnique or combination of techniques and any suitable information.

In some embodiments, the steps of block 926 can generate a historicalearthquake or seismic event model using any suitable earthquake orseismic event data. For example, the steps of block 926 can use datacataloging seismic characteristics of well-known historical earthquakesincluding, but not limited to, the 1906 San Francisco earthquake, the1923 Great Kanto earthquake (Japan), the 1964 Alaska earthquake, the1980 Campania (Italy) earthquake, the 1994 Northridge (California)earthquake and the 2017 Mexico City earthquake. In another example, thesteps of block 926 can catalog the frequency and severity (e.g., overallmagnitude, local intensity, local acceleration, etc.) of earthquakesalong the San Andreas Fault of southern California over a certainperiod. As a more particular example, the steps of block 926 can use anearthquake or seismic event dataset that records the time, date,epicenter location, magnitude, duration, maximum intensity and maximumacceleration for earthquakes from a given set of years, e.g., the years1900 through 2000. In other embodiments, the steps of block 926 can usea earthquake or seismic event dataset for earthquake or seismic eventfrom the year 1900 through the most recent year for which earthquake orseismic event data is available. In still other embodiments, the stepsof block 926 can use a earthquake or seismic event dataset forearthquake or seismic event from a predetermined first year agreed-tounder a contract through a predetermined final year agreed-to under thecontract.

In some embodiments, the steps of block 926 can further includesupplementing historical earthquake or seismic event data by generatingsynthetic earthquakes or seismic events and/or generating a historicalearthquake or seismic event model based at least in part on thesynthetic earthquakes or seismic events.

In some embodiments, the triggering process 900 includes a block 928having steps of generating an earthquake or seismic event damage modelbased on a historical earthquake or seismic event model. In someembodiments, the steps of block 928 can follow the steps of block 926,and the historical earthquake or seismic event model can be thehistorical earthquake or seismic event model generated by the steps ofblock 926. In some embodiments, the steps of block 928 can generate anearthquake or seismic event damage model based on the historicalearthquake or seismic event model using any suitable techniques orcombination of techniques and any suitable information.

In some embodiments, the steps of block 928 can generate an earthquakeor seismic event damage model by simulating seismic intensity and/orground accelerations and/or ground velocity based on the historicalearthquake or seismic event model. For example, the steps of block 928can simulate peak seismic intensity, peak ground acceleration, peakground velocity or other peak seismic characteristic in the historicalearthquake or seismic event model and associate the simulated peakseismic intensity or peak ground acceleration or other peak seismiccharacteristic with historical damage information.

In some embodiments, the triggering process 900 includes a block 930having steps of receiving seismic data if the process determines (e.g.,from the steps of block 924) that that seismic data should be sent forcertification (i.e., as denoted by arrow 932 in FIG. 9). In someembodiments, the steps of block 930 can receive seismic data using anysuitable technique or combination of techniques. For example, the stepsof block 930 can receive seismic data via a communication network (e.g.,the communication network 210 of FIGS. 6 and 7) from a seismic station709 or seismic station system 600 as described above. As anotherexample, the steps of block 930 can receive seismic data via acommunication network (e.g., the communication network 210 of FIGS. 6and 7) from a data server, e.g., the data server 702 of FIG. 7. Theseismic data received can be seismic data from a seismic station at thegeographic location of interest and can also include seismic data fromother geographic locations such as remote seismic stations.

In some embodiments, the triggering process 900 includes a block 934having steps of generating a certification report for the receivedseismic data from the geographic location of interest based on thehistorical earthquake or seismic event model, and/or the earthquake orseismic event damage model. In some embodiments, the steps of block 934can follow the steps of block 930. In some embodiments, the steps ofblock 934 can generate a certification report for the received seismicdata from the geographic location of interest based on the historicalearthquake or seismic event model (e.g., from block 926) and/or theearthquake or seismic event damage model (e.g., from block 928) usingany suitable technique or combination of techniques and any additionalsuitable information. For example, in some embodiments, the process 900and the steps of block 934 can generate a certification report byinputting (as denoted by arrow 936 in FIG. 9) the received seismic datain addition to information related to buildings in an area related tothe seismic data (e.g., construction class of the buildings, buildingheight, building occupancy, year of construction, and/or floor area)into the earthquake or seismic event damage model. As a more particularexample, if the seismic characteristics (e.g., seismic intensity oracceleration or velocity) from the seismic data are within apredetermined number of standard deviations from the seismiccharacteristics of an earthquake or seismic event predicted by themodel, the steps of block 934 can generate a certification report thatcertifies the seismic data. As another example, the steps of block 934can generate a certification report by comparing the received seismicdata (e.g., from block 930) with a seismic intensity predicted by thehistorical earthquake or seismic event model (e.g., from block 926). Asstill another example, the steps of block 934 can generate acertification report for the seismic data received from the geographiclocation of interest (i.e., “local seismic data”) by comparing the localseismic data to seismic data received from seismic stations 709 at othergeographic locations for the same event (i.e., “remote seismic data”),and determining if the seismic characteristics of the local seismic databear a predetermined relationship with the seismic characteristics ofthe remote seismic data. Such predetermined relationships can be set byreview of historic earthquake intensity data, historic earthquake damagedata, earthquake intensity models and/or earthquake damage models forthe location of interest and the location of the remote seismic station.In some embodiments, first seismic data considered to be local seismicdata from a first seismic station 709 to be certified in a first casecan be considered, in a second case, to be remote seismic data from aremote seismic station and used to certify second seismic data from thea second seismic station. As yet another example, the steps of block 934can generate a certification report based on earthquake or seismic eventdata received from a third party server 714, e.g., from USGS or FEMA.

In some embodiments, the triggering process 900 includes a block 938having steps of sending a certification report (e.g., as denoted byarrow 939 in FIG. 9). In some embodiments, the steps of block 938 canfollow the steps of block 934. In some embodiments, the steps of block938 can send the certification report using any suitable techniques orcombination of techniques. For example, the steps of block 938 can sendthe certification report to a data server (e.g., the data server 702 ofFIG. 7) via a communication network (e.g., the communication network 210of FIG. 7). The triggering process 900 may further include a block 940having steps of receiving the certification report sent by the steps ofblock 938. In some embodiments, the steps of block 940 can receive thecertification report using any suitable techniques or combination oftechniques. For example, the steps of block 940 can receive thecertification report from a communication network (e.g., thecommunication network 210 of FIG. 7) using a data server (e.g., the dataserver 702 of FIG. 7).

In some embodiments, the triggering process 900 includes a block 942having steps of determining if a contract has been met. In someembodiments, the steps of block 942 can follow the steps of block 940.In some embodiments, the steps of block 942 can determine if a contracthas been met using any suitable techniques or combination of techniquesand/or any suitable information. For example, the steps of block 942 candetermine if a contract has been met based on the received certificationreport, e.g., the certification report received from block 940. Forexample, the steps of block 942 can determine that a seismic intensityor a ground acceleration or other seismic characteristic contained inseismic data is greater than a threshold amount contained in a contractand that the certification report certifies that such seismic intensityor ground acceleration or other seismic characteristic is correct, andaccordingly determine that the contract has been met. As anotherexample, the steps of block 942 can determine that a seismic intensityor ground acceleration or other seismic characteristic contained inseismic data is greater than a threshold amount contained in a contract,and that the certification report does not certify that such a seismicintensity or ground acceleration or other seismic characteristic iscorrect, and accordingly determine that the contract has not been met.

In some embodiments, the steps of block 942 can determine if a contracthas been met by submitting the seismic data and certification report formanual review. For example, if the steps of block 942 determine thatseismic data includes a seismic intensity, ground acceleration, groundvelocity or other seismic characteristic that is higher than arespective threshold seismic intensity, ground acceleration, groundvelocity or other seismic characteristic contained in a contract, andthat the certification report certifies that the seismic data iscorrect, the steps of block 942 can then submit the seismic data and thecertification report for manual review.

In some embodiments, the triggering process 900 includes a block 944having the steps of triggering a payout of a contract. In someembodiments, the steps of block 944 can follow the steps of block 942 ifthe steps of block 942 determined that the contract was met. In someembodiments, the steps of block 942 can trigger a payout of the contractusing any suitable technique or combination of techniques. For example,the steps of block 942 can trigger a payout of the contract by sendinginformation to a contract payout server (e.g., the contract payoutserver 708 of FIG. 7). As another example, the steps of block 942 cantrigger a payout by processing an electronic transaction such as a bankdeposit, an electronic funds transfer, a direct deposit, sending adigital currency and/or any other suitable electronic transaction.

In some embodiments, at least some of the above-described blocks and/orsteps of the processes of FIGS. 8 and 9 can be executed or performed inany order or sequence not limited to the order and sequence shown in anddescribed in connection with the figures. Also, some of the above blocksand/or steps of FIGS. 8 and 9 can be executed or performed substantiallysimultaneously where appropriate or in parallel to reduce latency andprocessing times. Additionally or alternatively, some of the abovedescribed blocks and/or steps of the processes of FIGS. 8 and 9 can beomitted.

Referring now to FIG. 10, there is illustrated a system 1000 formanaging both wind speed data and seismic data that can be used inaccordance with some embodiments of the disclosed subject matter. In oneembodiment of system 1000, wind speed signals from anemometers 104 atwind station systems 100 and/or wind stations 209 are converted intowind speed data and seismic and/or acceleration signals fromseismometers 602 and/or accelerometers 604 are converted into seismicsignals at seismic station systems 600 and/or seismic stations 709. Inthis embodiment of the system 1000, the respective wind speed data andseismic data can be transmitted through a common communication network210 to data servers 202, 702, certification servers 206, 706 andcontract payout servers 208, 708, wherein the data servers 202 and 702can be implemented with the same or separate apparatus, thecertification servers 206 and 706 can be implemented with the same orseparate apparatus and/or the contract payout servers 208 and 708 can beimplemented with the same or separate apparatus.

Using the system 1000, a process is provided for triggering multi-factorevent payouts based on either wind speed data or seismic data or bothtypes of data in accordance with further embodiments of the disclosedsubject matter. Analogous in most respects to the process 500 of FIG. 5and the process 900 of FIG. 9, the multi-factor event triggering processcan receive multi-factor data including wind speed data, e.g., from windstations 209, and seismic data, e.g., from seismic stations 709. In someembodiments of the multi-factor triggering process, the multi-factordata can be received and stored at a data server 202, 702 according toprocesses substantially identical to those described for blocks 520,522, 920 and 922. In some embodiments of the multi-factor triggeringprocess, the data server 202, 702 can determine if the multi-factor datashould be sent for certification according to processes substantiallyidentical to those described for blocks 524 and 924. When sent forcertification, the multi-factor data can be received by a certificationserver 206, 706. In some embodiments of the multi-factor triggeringprocess, the certification server 206, 706 can generate historical stormmodels, wind speed damage models, historical earthquake or seismic eventmodels and earthquake or seismic event damage models according toprocesses substantially similar to those described for blocks 526, 528,926 and 928.

In some embodiments, the multi-factor triggering process can furtherhave steps of receiving multi-factor data if the process determines(e.g., from the steps of block 524, 924) that that multi-factor datashould be sent for certification (i.e., as denoted by arrows 532 and 932in FIGS. 5 and 9). The steps of receiving the multi-factor data can besubstantially similar to the processes described for blocks 530 and 930.In some embodiments of the multi-factor triggering process, acertification report can be generated for the received multi-factor dataaccording to processes substantially similar to those described forblocks 534 and 934. In some embodiments of the multi-factor triggeringprocess, a certification report can be sent (e.g., to a data server 202or 702) via a communication network according to processes substantiallysimilar to those described for blocks 538 and 938. In some embodiments,the multi-factor triggering process can receive the certification reportusing any suitable techniques or combination of techniques. For example,the certification report can be received from a communication network(e.g., the communication network 210) using a data server (e.g., thedata server 202 or 702).

In some embodiments, the multi-factor triggering process includes stepsof determining if a contract has been met according to processessubstantially similar to those described for blocks 542 and 942. In someembodiments, the multi-factor triggering process can determine if acontract has been met using any suitable techniques or combination oftechniques and/or any suitable information. For example, the steps candetermine if a contract has been met based on the received certificationreport covering wind speed data and/or seismic data. For example, thesteps of the multi-factor process can determine that a measured windspeed value contained in wind speed data is greater than a thresholdvalue contained in a contract and that the certification reportcertifies that such measured wind speed value is correct, and/or that ameasured seismic intensity value, a measured ground acceleration valueor a measured ground velocity value contained in seismic data is greaterthan a respective threshold value contained in a contract and that thecertification report certifies that such respective measured seismicintensity value, measured ground acceleration value, or measured groundvelocity value is correct, and thereupon determine that the contract hasbeen met. In some embodiments, a certification report can certify that arespective measured wind or seismic value is “correct” if the respectivemeasured value falls within predetermined parameters compared to one ormore certification control values specified in the contract. In someembodiments, the respective certification control values can berespective wind or seismic values predicted by a respective wind orseismic historical model or wind or seismic damage model. In some otherembodiments, the respective certification control values can berespective wind or seismic values received from one or morepredetermined remote wind or remote seismic stations. In one example,the predetermined parameters can be a predetermined number of standarddeviations, i.e., the measured values are considered “correct” if theyare within a predetermined number of standard deviations from thecontrol values, e.g., from the values predicted by the historical modelor damage model or received from the remote station. In another example,the predetermined parameters can be a predetermined percentagedifference, i.e., the measured values are considered “correct” if theyare within a predetermined percentage difference from the controlvalues, e.g., from the values predicted by the historical model ordamage model or received from the remote station. However, even if ameasured wind speed, seismic intensity, ground acceleration or groundvelocity contained, respectively, in a wind speed data or seismic datais greater than a threshold amount contained in a contract, the steps ofthe multi-factor triggering process can determine that a contract is notmet if the certification report does not certify that such a measuredwind speed, seismic intensity, ground acceleration or ground velocity iscorrect.

In some embodiments, the steps of the multi-factor triggering processcan determine if a contract has been met by submitting the wind data andseismic data and certification report for manual review. For example, ifthe earlier steps determine that wind data includes a wind speed that ishigher than a threshold wind speed contained in a contract, or theearlier steps determine that seismic data includes a seismic intensityor ground acceleration that is higher than a threshold seismic intensityor ground acceleration contained in the contract, and that thecertification report certifies that the relevant wind data and/orseismic data is correct, the steps of the triggering process can thensubmit the wind speed data and the seismic data and the certificationreport for manual review.

In some embodiments, the multi-factor triggering process includes thesteps of triggering a payout of a contract according to processessubstantially similar to those described for blocks 544 and 944. In someembodiments, the steps of triggering a payout of a contract can followthe steps of determining that the contract was met. In some embodiments,the steps can trigger a payout of the contract using any suitabletechnique or combination of techniques. For example, the steps of themulti-factor triggering process can trigger a payout of the contract bysending information to a contract payout server (e.g., the contractpayout server 208 or 708). As another example, the steps of themulti-factor triggering process can trigger a payout by processing anelectronic transaction such as a bank deposit, an electronic fundstransfer, a direct deposit, sending a digital currency and/or any othersuitable electronic transaction. In some embodiments, if two separatecontract criteria are satisfied by certified data, the multifactortriggering process can trigger two separate payouts, i.e., one payoutfor each criterion satisfied. In other embodiments, if two separatecontract criteria are satisfied by certified data, the multifactortriggering process can trigger only the higher one of the two separatepayouts (e.g., if the payout amounts for the two criteria aredifferent), or only a single payout (e.g., if the payout amounts are forthe two criteria are identical).

In still another aspect, secure measurement stations can be provided atparticular geographic locations to measure other natural and/or manmadephenomena events including, but not limited to, tsunami or tidal waves,volcanic ash or gas emissions, droughts, air pollution (also known as“smog”) levels or levels of specific pollutants at the particulargeographic locations, wherein the various phenomena event measurementsare received and converted into phenomena event data and stored inmemory in the secure measurement stations using apparatus and processesanalogous to those described herein for wind speed and seismic data.Further, the phenomena event data from the secure measurement stationscan be transmitted to a phenomena event data system including dataservers, certification servers and/or payout servers using apparatus andprocesses analogous to those described herein for wind speed and seismicdata. The phenomena event data system can provide apparatus andprocesses for receiving the phenomena event data analogous to thosedescribed herein for wind speed and seismic data and determining if theevent data needs to be certified. The phenomena data system can provideapparatus and processes for generating historical models of variousphenomena events and/or for generating damage models of variousphenomena events analogous to those described herein for wind speed andseismic data. The phenomena data system can provide apparatus andprocesses for triggering payouts triggering payouts analogous to thosedescribed herein for wind speed and seismic data. The phenomena datasystem can provide apparatus and processes for triggering payouts basedon the phenomena data from the secure measurement stations, either aloneor combined with wind speed data and/or seismic data from wind stationsand/or seismic stations, respectively.

In some embodiments, any suitable computer readable media can be usedfor storing instructions for performing the functions and/or processesherein. For example, in some embodiments, computer readable media can betransitory or non-transitory. For example, nontransitory computerreadable media can include media such as magnetic media (such as harddisks, floppy disks, and/or any other suitable magnetic media), opticalmedia (such as compact discs, digital video discs, Blu-ray discs, and/orany other suitable optical media), semiconductor media (such as flashmemory, electrically programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), and/or any othersuitable semiconductor media), any suitable media that is not fleetingor devoid of any semblance of permanence during transmission, and/or anysuitable tangible media. As another example, transitory computerreadable media can include signals on networks, in wires, conductors,optical fibers, circuits, any suitable media that is fleeting and devoidof any semblance of permanence during transmission, and/or any suitableintangible media.

Although the invention has been described and illustrated in theforegoing illustrative embodiments, it is understood that the presentdisclosure has been made only by way of example, and that numerouschanges in the details of implementation of the invention can be madewithout departing from the spirit and scope of the invention. Featuresof the disclosed embodiments can be combined and rearranged in variousways.

What is claimed is:
 1. A system, the system comprising: an externalcommunication network communicatively connecting one or more parametricstations, a certification server, and a payout server, wherein the oneor more parametric stations are located remotely from the certificationserver and the payout server; the one or more parametric stations, eachrespectively comprising: a parametric communication interface configuredto receive parametric data from a remote source, a parametric processorconfigured to: determine that the parametric data satisfies apredetermined condition, and control the parametric communicationinterface to transmit the parametric data to the certification server inresponse to the parametric data satisfying the predetermined condition;the certification server comprising: a certification processorconfigured to generate a certification report based on the parametricdata and data models related to the remote source from which theparametric data was received, and a certification communicationinterface configured to transmit the generated respective certificationreport to the payout server; and the payout server comprising: a payoutprocessor configured to: determine that terms of a respective associatedcontract are satisfied based on the respective certification report, andtrigger a payout based on the terms that are satisfied based on therespective certification report.
 2. The system of claim 1, wherein theparametric data from a remote source comprises parametric data capturedfrom one or more sensors.
 3. The system of claim 2, wherein the datamodels include historical parametric models for the one or more sensors.4. The system of claim 1, wherein the parametric data from a remotesource comprises information indicating that the predetermined conditionis satisfied.
 5. The system of claim 4, wherein the data models includehistorical condition models for decisions made by the remote source. 6.The system of claim 1, wherein: a parametric station further includesone or more sensors configured to capture parametric data, and theparametric processor is further configured to: determine that thecaptured parametric data satisfies a predetermined condition, andcontrol the parametric communication interface to transmit theparametric data to the certification server in response to theparametric data satisfying the predetermined condition.
 7. The system ofclaim 6, wherein the data models include historical parametric modelsfor the one or more sensors at the parametric station.
 8. A wind eventsystem, the wind event system comprising: an external communicationnetwork communicatively connecting one or more wind parametric stations,a certification server, and a payout server, wherein the one or morewind parametric stations are located remotely from the certificationserver and the payout server; the one or more wind parametric stations,each respectively comprising: a parametric communication interfaceconfigured to receive wind parametric data from a remote source, aparametric processor configured to: determine that the wind parametricdata satisfies a predetermined condition, and control the parametriccommunication interface to transmit the wind parametric data to thecertification server in response to the wind parametric data satisfyingthe predetermined condition; the certification server comprising: acertification processor configured to generate a certification reportbased on the wind parametric data and wind data models related to theremote source from which the wind parametric data was received, and acertification communication interface configured to transmit thegenerated respective certification report to the payout server; and thepayout server comprising: a payout processor configured to: determinethat terms of a respective associated contract are satisfied based onthe respective certification report, and trigger a payout based on theterms that are satisfied based on the respective certification report.9. The wind event system of claim 8, wherein the wind parametric datafrom a remote source comprises wind speed data captured from one or moreanemometers.
 10. The wind event system of claim 9, wherein the wind datamodels include historical wind speed models for the one or moreanemometers.
 11. The wind event system of claim 8, wherein the windparametric data from a remote source comprises information indicatingthat the predetermined condition is satisfied.
 12. The wind event systemof claim 11, wherein the wind data models include historical windcondition models for decisions made by the remote source.
 13. The windevent system of claim 8, wherein: a wind parametric station furtherincludes one or more anemometers configured to capture wind parametricdata, and the parametric processor is further configured to: determinethat the captured wind parametric data satisfies a predeterminedcondition, and control the parametric communication interface totransmit the wind parametric data to the certification server inresponse to the wind parametric data satisfying the predeterminedcondition.
 14. The wind event system of claim 13, wherein the wind datamodels include historical wind speed models for the one or moreanemometers at the wind parametric station.
 15. A seismic event system,the seismic event system comprising: an external communication networkcommunicatively connecting one or more seismic parametric stations, acertification server, and a payout server, wherein the one or moreseismic parametric stations are located remotely from the certificationserver and the payout server; the one or more seismic parametricstations, each respectively comprising: a parametric communicationinterface configured to receive seismic parametric data from a remotesource, a parametric processor configured to: determine that the seismicparametric data satisfies a predetermined condition, and control theparametric communication interface to transmit the seismic parametricdata to the certification server in response to the seismic parametricdata satisfying the predetermined condition; the certification servercomprising: a certification processor configured to generate acertification report based on the seismic parametric data and seismicdata models related to the remote source from which the seismicparametric data was received, and a certification communicationinterface configured to transmit the generated respective certificationreport to the payout server; and the payout server comprising: a payoutprocessor configured to: determine that terms of a respective associatedcontract are satisfied based on the respective certification report, andtrigger a payout based on the terms that are satisfied based on therespective certification report.
 16. The seismic event system of claim15, wherein the seismic parametric data from a remote source comprisesseismic parametric data captured from one or more seismic sensors oraccelerometers.
 17. The seismic event system of claim 16, wherein theseismic data models include historical parametric models for the one ormore seismic sensors or accelerometers.
 18. The seismic event system ofclaim 15, wherein the seismic parametric data from a remote sourcecomprises information indicating that the predetermined condition issatisfied.
 19. The seismic event system of claim 18, wherein the seismicdata models include historical condition models for decisions made bythe remote source.
 20. The seismic event system of claim 15, wherein: aseismic parametric station further includes one or more seismic sensorsor accelerometers sensors configured to capture seismic parametric data,and the parametric processor is further configured to: determine thatthe captured seismic parametric data satisfies a predeterminedcondition, and control the parametric communication interface totransmit the seismic parametric data to the certification server inresponse to the seismic parametric data satisfying the predeterminedcondition.